In my view they are Postgresql and sqlite. MySQL is supported well but the databse itself has issues like the max size of text fields and cannot do multicolumn migrations per transactions.
MSSQL and Oracle cannot do pagination (not a web2py issue). web2py tries to go around the limitation but it may have problems with paginations on JOINS. Firebird seems to work all right but 'password' is a reserved keyword so Auth must use 'password2'. annoying. GAE works fine but we do not support some of their properties (notably listproperty) and they do not support many of the relational features that one would like (multitable transactions, like, or, joins, in, date manipulations). On Sep 29, 2:31 pm, Yannick <ytchatch...@gmail.com> wrote: > Hello mate, > I have a simple question, > Since i start working with Web2py I'm using MySql as back-end which is > good and running perfectly... I'm still looking for room to improve > and wondering about what back-end suit best with Web2py: It is GAE ? > Oracle ? MySql ? > > Thanks for letting me know what you think... > > Cheers, > Yannick P. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
