There is one problem though. The delete cascade cannot be done in a trasaction so there is the possibility that if many entities are deleted and takes time and the request timeout, you end up with partial deletion. We'll have to try it.
On Jan 4, 9:53 pm, mdipierro <[email protected]> wrote: > It will probably be transparent. No special code. I will try implement > this tomorrow. > > On Jan 4, 9:35 pm, yamandu <[email protected]> wrote: > > > First, thanks so much again for quick answer Massimo! > > > But I am not sure if I understood. Will be a there way to do so? > > Will it be normally transparent or have to write special code to GAE? > > > On Jan 4, 4:04 pm, mdipierro <[email protected]> wrote: > > > > I found a way to implement this db.delete(top.bottom_set) > > > I will add it to the new DAL. > > > > On Jan 4, 12:00 pm, mdipierro <[email protected]> wrote: > > > > > No it does not. Now that you bring this up, we could implement it as > > > > we did for sqlite but because of GAE limitations in accessing no more > > > > than 1000 records at the time this may be very slow and inefficient. > > > > It may also fail if you have a lot of referencing records. I think on > > > > GAE you have to delete them manually. > > > > > On Jan 4, 11:25 am, yamandu <[email protected]> wrote: > > > > > > Maybe it´s another stupid question but I need to be sure. > > > > > Does delete cascade work on GAE? > > > > > If no there´s a recommended way to do this? Or a turn around? > > -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
