I myself have not missed JMS. XML-RPC covers for any service I need to provide. I would recommend SQLAlchemy instead of SQLObject it will freshen you up compared to Java.
On 8/14/06, Peter Bunyan <[EMAIL PROTECTED]> wrote:
I'm using MySQL and since the user can create activities I need to rely
on the db for its unique constraint. Not just that but the above code
does not work either since None in not returned but an exception. I
don't want to roll back the code but continue - I did not start the
transaction but the framework did. The exception should not invalide
the transaction - I don't know what else has gone on in the transaction
or how deep my work is! This pattern should work - something in TG or
SQLObject is stopping it.
You are right, catching all exceptions is not a good thing. I do not
like that I have to catch a MySQL specific exception! I would like the
code to be db agnostic where ever possible. The framework should wrap
logical errors!
Again the documentation about transaction is sketchy. I assume that the
framework will rollback on exceptions or try to commit - it causes
problems when I do that in my code as a commit or rollback is called
again! That too causes and exception!
Besides that I am blown away by TG - CherryPy, SQLObject and Kid are a
breath of fresh air after J2EE. If only python had JMS and JTM I would
be happy.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
