Lot of hosting doesn't support Postgres. For example, go daddy. https://support.godaddy.com/help/category/67/web-hosting-databases
That said, I realize, go daddy is not a typical python hosting platform. Just playing devils advocate here. Also, open source product wouldn't be as secured as MYSQL since its open source. But I do agree with the rest. -Ron On Monday, April 6, 2015 at 12:52:34 PM UTC-4, Derek wrote: > > I have to take issue with your 'not for production' criticism of sqlite. > > https://www.sqlite.org/whentouse.html > > It has changed a lot since 2009 and you should really get familiar with it > if you are going to use it. > > Also, concerning the data types, SQLITE only supports 4 data types. NULL, > INTEGER, REAL, TEXT, and BLOB. I'm not counting NULL as a data type, but > whatever. If you are going to use SQLITE then you should understand how it > stores data. > > http://www.sqlite.org/datatype3.html > > That said, my choice would be Postgres because it is more ANSI compliant > and more predictable. Not to mention that the python bindings for Postgres > are much better than for MySQL. > > > On Monday, April 6, 2015 at 1:47:46 AM UTC-7, Philip Kilner wrote: >> >> Hi, >> >> On 05/04/15 12:07, Wellington Faria wrote: >> > I would like to know wich is better database to use in web2py? Mysql >> > or postgre? >> > >> >> I would suggest very strongly that Postgres is a better option. >> >> The reason for this is that Postgres runs its migrations (e.g. DDL) >> inside a transaction, so migrations are much more robust. Postgres has >> many advantages over MySQL, and MySQL has a couple of complexities >> (choice of storage engines) that I don't care for, but the robustness of >> migrations is the one that is particular to web2py, given web2py's >> automated migrations. >> >> I see that you have been advised in another response to use SQLite, but >> I would suggest not doing so for two reasons: - >> - First, SQLlite is not suitable for production, and it is much better >> practice to develop against the database you intend to deploy on. >> - Second, SQLite does not fully migrate existing data when you e.g. >> change the type of a field, which can cause confusion or even scrambled >> data. >> >> SQLlite's accessibility and the fact that it requires no configuration >> make it a great choice to have preconfigured in web2py, but it is not >> the best choice for non-trivial development, and definitely not for >> production. >> >> HTH >> >> >> -- >> >> Regards, >> >> PhilK >> >> >> 'a bell is a cup...until it is struck' >> >> -- 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/d/optout.
