meta user
network profile
| bio | website | |
|---|---|---|
| location | Wisconsin | |
| age | ||
| visits | member for | 8 months |
| seen | Apr 2 at 14:08 | |
| stats | profile views | 1 |
I am PHP Website Developer who enjoys all aspects of web design and development.
I enjoy helping answering some questions on SO and thankful to get the occasional help from others.
|
Oct 5 |
comment |
ORDER BY on aggregate field on a closure table giving unexpected results Excellent explanation. I figured there was some kind of re-ordering going on before the sorting but I wasn't sure where that was happening. Your explanation will help me troubleshoot this in the future. Thanks much! |
|
Oct 5 |
accepted | ORDER BY on aggregate field on a closure table giving unexpected results |
|
Oct 4 |
asked | ORDER BY on aggregate field on a closure table giving unexpected results |
|
Sep 26 |
comment |
Product Attribute List Design Pattern Indeed. I'm going "doh" that I didn't see doing a cross table of product to attribute. Probably a case of over thinking especially after immersing design patterns and theories. Also, my DBA experience is basic and doing more with prepared statements is something I need, so your inclusion is most helpful. And this answer has helped break down that "writers block" I was having so I can move on with this project, which makes my day. =) |
|
Sep 26 |
awarded | Scholar |
|
Sep 26 |
accepted | Product Attribute List Design Pattern |
|
Sep 26 |
comment |
Product Attribute List Design Pattern +1 - A fantastically written answer. I'm still taking a few moments to re-read and digesting this answer before accepting. It does look like a good solution to my question about joins and product attributes and even goes above and beyond with examples of pivots and prepared statements. So, I'll start with a +1 for that. =) |
|
Sep 26 |
awarded | Supporter |
|
Sep 25 |
awarded | Citizen Patrol |
|
Sep 25 |
revised |
Product Attribute List Design Pattern added 181 characters in body |
|
Sep 24 |
comment |
Product Attribute List Design Pattern I am wondering if it would be fine having all these attribute values joined to the product type table if I ultimately create a "view" on top of it? |
|
Sep 22 |
comment |
Product Attribute List Design Pattern Sorry, it Should be "attribute value". The idea that you have a table listing all the values allowed for an attribute. Ie. here is a list of 10 colors that this product type can be. These 10 are the "authorize" values some one could choose. |
|
Sep 21 |
awarded | Editor |
|
Sep 21 |
revised |
Product Attribute List Design Pattern Added an extra bullet in my ending notes based on the first comment |
|
Sep 20 |
comment |
Product Attribute List Design Pattern Good question. It will start small 3-4 but potentionally grow larger to 10+ |
|
Sep 20 |
awarded | Student |
|
Sep 20 |
asked | Product Attribute List Design Pattern |
