network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 4 months |
| seen | Feb 19 at 13:34 | |
| stats | profile views | 5 |
PHP, HTML, Javascript, CSS Grails, Java
|
Feb 19 |
awarded | Commentator |
|
Feb 19 |
accepted | Create a VIEW that spans 3 tables |
|
Feb 19 |
comment |
Create a VIEW that spans 3 tables I went with Option 2. Using "explain" also made it seem better to use option 2. |
|
Feb 19 |
comment |
Create a VIEW that spans 3 tables "There's not really a strong case here for doing this with views" - I'm doing this simply to make coding simpler, instead of storing this query. |
|
Feb 18 |
revised |
Create a VIEW that spans 3 tables added 651 characters in body |
|
Feb 18 |
revised |
Create a VIEW that spans 3 tables added 64 characters in body |
|
Feb 18 |
revised |
Create a VIEW that spans 3 tables deleted 99 characters in body |
|
Feb 18 |
asked | Create a VIEW that spans 3 tables |
|
Dec 30 |
comment |
MySQL Workbench sync keeps requesting the same changes 5.1.53 on OSX .. |
|
Dec 27 |
comment |
MySQL Workbench sync keeps requesting the same changes Yes, 5.2.44 for OSX |
|
Dec 27 |
asked | MySQL Workbench sync keeps requesting the same changes |
|
Nov 20 |
comment |
View for a MANY_MANY_MANY relationship Edited my answer. Is this a good solution now? |
|
Nov 20 |
awarded | Editor |
|
Nov 20 |
revised |
View for a MANY_MANY_MANY relationship deleted 15 characters in body |
|
Nov 19 |
comment |
View for a MANY_MANY_MANY relationship I don't know why I picked LEFT JOIN. Would INNER JOIN be more appropriate? |
|
Nov 19 |
answered | View for a MANY_MANY_MANY relationship |
|
Nov 19 |
comment |
View for a MANY_MANY_MANY relationship Does this look good? CREATE VIEW category_url AS
(SELECT DISTINCT category.id AS category_id, url.id AS url_id
FROM category
LEFT JOIN category_tag ON category_tag.category_id=category.id
LEFT JOIN url_tag ON url_tag.tag_id = category_tag.tag_id
LEFT JOIN url ON url.id = url_tag.url_id) |
|
Nov 19 |
asked | View for a MANY_MANY_MANY relationship |
|
Jul 9 |
awarded | Supporter |
|
Jul 9 |
comment |
Foreign key with multiple table options Sounds good. Although I'm not sure I understood "but maintain the object_type (for partitioning later)". |
