At 02:08 PM 5/17/2009, you wrote:
>--- In ><mailto:flexcoders%40yahoogroups.com>[email protected], >Laurence MacNeill <lmacne...@...> wrote: > > > > At 06:26 PM 5/15/2009, you wrote: > > > > > > >How that is different from a database table with 25 rows? > > > > Because it just is. LOL With 25 rows, you have 25 separate > > records. This is 25 columns within a single record. There are other > > columns too, not just these 25. > >It seems to me that unless this is a system that has been in long >production (don't laugh, y'all, I've seen some tables structured >exactly this way in enterprise scale databases), that you would be >well advised to change your database structure so that it _is_ rows >instead of columns. This system's been this way for many years, but I'm completely re-writing it, so moving that info into a separate table with rows instead of columns is totally do-able. (In fact, I came up with that idea after Mark's comment about the rows vs. columns.) >Now it becomes amazingly easy to populate your tables from the >array. That's one reason normalization was invented. It's a great >design pattern. The only thing I don't know how to do is have a CFC loop thru the array to store each element in the DB. Can you help? >HTH; And what does HTH mean? :-) Thanks, Laurence MacNeill Mableton, Georgia, USA
