Hi Derek,
On 06/04/15 17:52, Derek wrote:
I have to take issue with your 'not for production' criticism of sqlite.
OK, but...
https://www.sqlite.org/whentouse.html
...just to be clear, that comment was in the context of web2py use, not
generally.
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
Are you suggesting that the notes in the web2py book: -
http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#SQLite
...are in need of updating?
Either way, given the way that web2py handles migrations, I'd rather
avoid those complexities entirely by using a more robust platform than
have to familiarise myself with quirks and work around them.
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.
Both good points, but based on my personal experience of using all three
databases, the robustness of web2py's migrations is the deciding factor
for me: -
- SQLite works well when used within its limitations, but in my own
usage there has always been a superior alternative available, and SQLite
is the only one of the three where I have ended up with an
un-salvageable migration. It has only happened a couple of times, but it
cost me some time.
- MySQL is very robust, but when a migration fails, it can still be time
consuming.
- Postgres is *extremely* reliable, and I don't think I can recall an
instance of a migration problem.
Postgres has saved me from myself enough times that I'd always use it
with web2py when available, but where I've had to use MySQL (at
PythonAnywhere, and on Google App engine in the form of CloudSQL) it has
been robust.
There isn't a right or wrong answer to this and both platforms work (as
does SQLite, with some gotchas), but the OP asked for opinions as to
which of the two worked better (SQLite was not mentioned by the OP), and
I hope that our different experiences and perspectives have been useful.
--
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.
