"goff" <[EMAIL PROTECTED]> writes:
this is not always correct. The modul classes (SQLObject in this case) are responsible for keeping the database in a consistent state, and consistency can include certain value checks. SQL itself supports constraints which do nothing else. So, how do I check constraints on 2 tables connected by a RelatedJoin in SQLObject?
Search for "object relational impedance mismatch" (without quotes) on Google. Also search for MVC. If you're inserting logic inside your model you're breaking the MVC model. This might be good or bad, it depends on your goals and what you want. I understand your position and I am one of the people that puts all what is possible inside the database. You have to choose one of: - easy to use - multidatabase You can't have both. With newer versions of SQL Object you have means to pass extra commands to be executed after table creation, but since those are strings you'll have to find your own way to handle multiple databases. On the other hand, SO is an open source project and they are very receptive to patches that contribute new functionalities (if it goes with tests then you have more chances that it gets applied). I use the ORM layer to make my life easy. I don't want -- and don't need -- multidatabase support. I chose my DB, I have lots of things that SQL Object doesn't manage -- and doesn't know that it exist inside the DB -- and everyone is happy. SQL Alchemy is a bit better on this area, but isn't perfect as well (for example it can't handle columns that are arrays). -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
