On 11/8/06, iain duncan <[EMAIL PROTECTED]> wrote: > > 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? >
Not quite what you're looking for but my SimpleBlog series[1] gives you a practical application of SA and shows you a few of the nice features that you can use. Hopefully it can help you compare it against SO. [1]: http://www.splee.co.uk/category/simpleblog/ I always use SA now for the same reasons as Karl. Yes, the table/object definitions are more verbose, but for the relative amount of time one spends coding a model in SA over having to overcome some of SO's limitations further down the line I consider it a very small cost. Lee -- Lee McFadden blog: http://www.splee.co.uk work: http://fireflisystems.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
