iain duncan <[EMAIL PROTECTED]> writes: > How do I keep caching off in gears?
If you don't tell SQL Object to explicitly use cache it won't. :-) TG also wraps each exposed (!!!) method inside a transaction. You'd have to guarantee that other methods that aren't exposed and touch the DB are also within a transaction. This will make SQL Object to go to the database for data. >> Ensure that you're always coding it safe and using transactions. > > Hmm, shouldn't the rdbm be taking caring of locking on it's own? I mean, > how is there any difference to the rdbm between multiple threads of one > app hitting the same table and threads of different apps doing the same > thing? Databases allow developers to explicitly lock tables and rows (it depends on your database). One example of explicit lock is "SELECT FOR UPDATE" in PostgreSQL. If you're just using basic SQL then you shouldn't have problems... -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
