> On Thursday, March 12, 2015 at 4:53:18 PM UTC+1, Anthony wrote: >> >> On Thursday, March 12, 2015 at 11:20:15 AM UTC-4, lucas wrote: >>> >>> i thought that could be a connection or association that web2py can make >>> internally but above the database limitations. that should be doable no? >>> >> >> Well, as Niphlod pointed out, you can still use the IS_IN_DB validator to >> maintain the referential constraint from the app side. You won't get >> automatic cascading, but I suppose you could handle that with an >> _after_delete callback. Perhaps some of this could be automated by the DAL. >> >> > I don't think it'll be safe, because there's no way to support a callback > in the same transaction on different dbs, hence there's no way to preserve > integrity. >
Within the context of a web2py request, wouldn't there be two transactions open (one for each database)? In that case, at least if the request results in an error, both transactions would be rolled back. Anthony -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
