If you look at that more closely, you'll see it is only for translating Django/SQA models to web2py DAL models. Once you have the models, you still need to use web2py DAL syntax for all database operations, and the DAL still drives all the communication with the database (so it won't magically allow you to communicate with databases not already supported by the DAL).
Anthony On Saturday, February 1, 2014 3:04:34 AM UTC-5, damond...@gmail.com wrote: > > Hi, > > I stumbled upon an interesting but fairly old Massimo post: > http://web2py.com/AlterEgo/default/show/189 > > From my limited understanding, it looks like a concise and elegant way of > "wrapping" Django or SQLAlchemy models for reuse/call inside web2py. > > I am wondering whether this approach could be used as a bridge allowing > one to access from web2py, databases for which: > > - no web2py DAL is available > > - but a Django or SQLAlchemy ORM is available, > > without having to write a web2py DAL from scratch. > > For example, could one uses Massimo’s trick with the apparently available > django-redshift or sqalchemy-redshift ORMs to access AWS redshift from > web2py without having to write a specific web2py-redshift DAL. > > Has anyone tried something along these lines? Any success? Or is it a bad > idea? Or I am totally confused? :). > > Thanks a lot. > > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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.
