Hi all - I'm starting a project in R to write an ORM along the lines of SQLAlchemy (but minified). I wanted to solicit opinions on a few subjects: 1) What is best way to start and what are the 'best' places to safely cut corners and drop functionality? 2) Are there any components for which I'd want to consider diverging from SQLAlchemy's approach?
Some obvious language-specific implementation issues exist, but I anticipate those being resolvable with some thought. My goal is to get something up and running in a few hundred hours (leading me to question 3) is that sane?) that would necessarily be very limited in scope: it would not support table creation and only have a dialectical backing for MySQL. Many other components I could leave as stubs. In any case, I want to avoid design decisions that will limit future extensibility. Thanks! -- Rob -- You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en.
