I think this would be helpful to people like me, who is not an SQL or database expert, but doesn't want to use SQLAlchamy because it's too heavy. A lightweight ORM sounds like a good addition for a lightweight web framework.
On 12/25/07, Anand Chitipothu <[EMAIL PROTECTED]> wrote: > > On Dec 26, 2007 1:29 AM, Aaron Swartz <[EMAIL PROTECTED]> wrote: > > > > One of the things I like most about web.py is that SQL stuff is done > > in SQL, not Python. If you want to do something about this, what about > > picking some generic subset of SQL and writing translators to the > > various particular DBs? That way the schemas can continue to be > > written in SQL but can easily be translated to the app-specific DB. > > I am trying solve 2 problems. > > 1. DB Neutral schema > 2. Build schema by picking tables from multiple places. For example, > you may want to include session table from web.py in your schema. > > Probably, the first problem can be solved if we pick a translator. > What about the second. > How should the session table be represented in web.session. It is too > ugly to say, the schema for session table is available in some > docstring, take that and add to your schema.sql. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
