You can try adding some Asserts and overriding the validate() method of your property classes to check for data corruption. This should give you a better idea of what goes wrong and when. http://googleappengine.blogspot.com/2009/07/writing-custom-property-classes.html
On Nov 20, 11:30 pm, ussuri <michael.glas...@gmail.com> wrote: > On Nov 19, 9:57 pm, Julian Namaro <namarojul...@gmail.com> wrote: > > > The datastore is 100% reliable even if the datastore Java/Python APIs > > might not be. > > > What framework and libraries do you use? Is this live on appspot.com > > or the local dev server? It looks like there is an unauthorized write > > somewhere. > > > If you can reproduce the problem consistently, try to locate it by > > gradually shutting down parts of your code. > > this is live on appspot.com, using Python API. I cannot reproduce the > problem. I just notice occasional data corruption - it was rare like > 1-2 records out of thousands in a month, but two day ago I got a whole > bunch, as described in the original post. Can it be that occasionally > __key__ gets translated erroneously to point to a different record, > and then somehow the link becomes persistent in the textproperty > field? -- 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-appeng...@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=.
