1) if you can't reproduce the error with a specific "line" of your code
that triggers it, then is quite unuseful to try:catch every single db
operation.
BTW, this is what you'd need to do
try:
db(somequery).select()
except:
#handle the exception
pass
try:
db(somequery).update(somefield='something')
db.commit()
except:
db.rollback()
#handle exception
2. Pretty much anything else beside Access and maybe Firebird embedded.
<opinion personal="true">
I'm a strong user (believer, evangelist, etc) of Postgresql, that is by far
the most SQL compliant, extensible, hookable, opensource mvcc rdbms out
there. On web2py's side, it's maybe the most tested.
That being said, Mysql support is there too, if you want to jump on the
Mysql (better to jump on the MariaDB one for sure) bandwagon for any
reason. When you'll face strange lockings, outrageous execution times,
transaction isolation problems, unsupported "rather standard queries", etc,
and no-one will be able to explain the reasons behind those issues, you'll
remember "Niphlod said that" :-P .
I saw too many people jumping off cliffs for choosing Mysql too early in
the process pushed by **buzzwords** and **benchmarks** realizing too late
that "if mysql really worked out as advertised ...." they wouldn't had to
switch backends.
</opinion>
>
--
---
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/groups/opt_out.
