What if it's 9 fields? (Just Kidding). Thanks -
I think I will retain the normalized form and possibly create a function that scans a table that maintains the relationships between tables with the table names and key fields so I don't have to deal with updating the names and queries everywhere every time I add or remove a table or key field. Creating the record from all related tables one table at a time. A kind of data dispatch. On Oct 6, 10:19 am, mdipierro <[email protected]> wrote: > It depends on how many you need per page. If more than 10 I would use > option 1 (denormalize) and if less than 10 I would go with option 2. I > just made up the number 10. > > On Oct 6, 8:38 am, "Michael - afewtips.com" <[email protected]> > wrote: > > > I understand that inner joins on GAE are not allowed, so what is the > > best practice for > > retrieving data from related tables? > > > Forget normalizing and just add the related data to the record when > > the record is added? > > > or > > > Keep the data normalized and every time I need to show the data for a > > bicycle, go get the brand name from the brands table? > > > How do most get around the no inner join limitation? > > > Thanks > > Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
