> If you take into account what's said in this talk - that basically the ORM >>> and the CORE in SQLA are 2 separate beasts - than if follows what I've been >>> saying here, that the web2py-DAL is equivalent just to the CORE, and has no >>> features that the ORM provides whatsoever. >> >> >> I'm not sure that follows. The web2py DAL has a lot of features that >> might otherwise be found in an ORM. I'm not very familiar with SQLA, but I >> suspect the DAL has some features not present in CORE but similar to >> functionality included in the ORM. >> > > I wouldn't be so sure about that... > You should really check out the links I've posted in this thread - > SQLA-Core is a fully-fledged DAL. Reddit is using it alone, without any of > the ORM level... >
Well, I did say I "suspect", not that I'm sure, but does it have things like migrations, automatic file uploads/retrieval, recursive selects, automatic results serialization into HTML, virtual fields, computed fields, validators, field representations, field labels, field comments, table labels, list:-type fields, JSON fields, export to CSV, callbacks, record versioning, common fields, multi-tenancy, common filters, GAE support, and MongoDB support? > And again, it may be a matter of semantics, but there is no ORM feature in > the DAL - I've been going over the documentation and asking lost of > questing talking to Massimo - it's pretty conclussive - iweb2py's DAL > is exclusively-stateless... > I didn't say there were ORM features in the DAL, just that it includes features that you might otherwise expect to find in an ORM (e.g., something like virtual fields). In other words, some of what you get with that 20,000+ lines of ORM code might be functionality that is in fact available in the web2py DAL. Also, note that it might be the case that some of the features of the SQLA ORM that you find appealing don't necessarily require an ORM pattern per se but could possibly be implemented within the context of a DAL (i.e., just because SQLA does it via an ORM doesn't mean that's the only way). > You might also consider trying SQLA directly in place of the DAL >> > > I know that, but well, you see, there lies the problem - I DON'T want... I > love the DAL too much - wouldn't change it for anything! :) > (not even SQLA-Core...;) ) > But if you use an ORM built on top of the DAL, you won't be using the DAL API anyway, so what would you miss? Or are you saying you would still want to use the DAL for a significant portion of code and only move to the ORM for select parts of the application? Anyway, it may nevertheless be a useful exercise to start by using SQLA for some project just to see if it really delivers on the promises you believe it is making. Anthony -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
