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.
