If you have a way to precompute something to use as a key-name this is significantly less of an issue. The transaction repeating would not result in duplicate record being created that way.
Robert On Sat, Jul 30, 2011 at 12:39, Heiko Roth <r...@egotec.com> wrote: > > > On 26 Jul., 07:23, Robert Kluin <robert.kl...@gmail.com> wrote: >> Hi Pol, >> Generally you will probably want to execute it again. >> > > No. I've got the problem for time registration. We got an exception > that the transaction failed, so we do it again which can result in > duplicate (and more) datastore entries which is bad. Because now there > are duplicate bookings and so duplicate working time... > > It's a disaster that the program gets a transaction failed while the > transaction didn't doing another insert resulting in a mess. > But ignoring the exception can result in now datastore entry. > > So we have catch the exception, do a select and repeat the insert if > it didn't happen by now. > And that we have to do for any insert ...... > > I'm frustrated. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
