> > SO gives you more terse model syntax and catwalk. SA handles the hard > > cases better. > > Could anyone give examples ( perhaps these could be saved for docs ) of > where they feel the switch point is in terms of db cases? IE specific > instances of what you might need to be doing to justify the extra > overhead of SA?
For example, I have established that I will at least be using some Many-To-Many tables where the primary key is a combination of foreign keys, and that I'll need joins between that and some other tables. I would think this would not be too much for SO would it? I may later even want to integrate with a nasty old Filemaker database on windows machines using ODBC, but that is optional. Would probably add value to the contract though, if I decide I want to go there. :\ Thanks Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
