If you are not comfortable with django ORM you can also use SQLalchemy . Use that in web2py first to verify your model. And then you can copy and replace in django. Here is a way to replace the django ORM with SQLAlchemy.
http://lethain.com/replacing-django-s-orm-with-sqlalchemy/ You will be in luck when they have a way to use pydal in django. But for now, this may be another option to bridge the gap between two. On Wednesday, March 16, 2016 at 8:15:55 AM UTC-4, Bernard Letourmy wrote: > > Hello, > Took me around 2 months working on a new project from scratch to feel > nearly as comfortable with django as I was in web2py (after having enjoyed > web2py for 2+ years) > Although prepare to feel quite lot of pain along the way such > As when you keep repeating yourself with declaring and connecting routes, > controller (sorry view there) and templates till you find your own way to > auto generate the relations > Prepare to cry about batteries missing, such as: > - default user system with authentication views included, simple default > REST api support etc, > -nice and automatically configured appadmin with dal query, g not only > basic CRUD) > - a scheduler > - having to always find from where the hell you need to import that > class you use every day... > - having to find it in a manual splitted in chapters without a nice table > of content and good index system that force you to use Google even when > you know it's in the manual. > > You''ll also miss the power and clean syntax of pydal. You will see when > you will try to do your first join with django orm... > But ok once accustomed to the silly __ _id field__gte=x notations using > keywords argument instead of the clean field object and standard Python > Operators of pydal > You will enjoy quite powerful object oriented interface on your models. > With automatic reverse relation generations, very nice way to extend the > default model classes. > Basically a lot of choices at all stages either inside the framework for > different ways to do the same thing or out there when it comes to find a > plugin (an app in django) that provides the missing feature. > These being both advantages and inconvenience, explaining that it will > take certainly longer to be fully up and running with django than with > web2py > > Forgot one thing that's really nice with django: > the migration system. It's less 'automatic' then web2py's one but more > powerful and reliable in my opinion as it allows forward and backwards > migration and stores its meta data in the DB instead of the filesystem > itself allowing you to easily switch DB backend and migrate them from the > same Dev env for ex. > And one thing less nice > The core dev community is quite opiniated/ and stuck on the by design > limitations... > With the view/template system that force you to learn a new language with > expression being very restricted subset of Python > And force to develop yourself most of the basic filter needed. > Then quite a lot of won't fix issues or request for feature some > repeatidely asked for 10years > > But I do quite like django also :) > > Bon courage for your learning > Bernard > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
