Hi,

We determined the issue here was that the carriage returns in the data
viewer were not being validated when the delete request was called.
Removing the return in the query fixed the issue.

-Marzia

On Sat, Jan 17, 2009 at 10:15 AM, James Ashley <james.ash...@gmail.com> wrote:
>
> This sounds to me like something that should be reported as a bug.
> And whoever wrote that error message should be punished with at least
> 10 papercuts.
>
> But that's just me.  <G>
>
> On Jan 11, 3:33 pm, "murexconsult...@googlemail.com"
> <robin_ow...@hedge-row.co.uk> wrote:
>> There was a bug in my app and some bad data got into the Datastore.
>>
>> So I want to delete some data. The models have a number of items so
>> rather than paging through them all 20 at a time to find it I ran the
>> GQL query:
>> SELECT * FROM UserUpdates
>> WHERE windAngle=328
>>
>> This returns one row as expected. I then click on the tickbox beside
>> it and click on Delete.
>>
>> I then get a dialog box asking if I am sure to which I say yes.
>>
>> I then get the error displayed in a red box at the top saying "The URL
>> to forward to once the request is fulfilled" - Yes the error is a
>> partial sentence and makes no sense.
>>
>> The item is NOT deleted.
>>
>> This is happening to all 4 of my models. However 2 of them only have a
>> few hundred entries, so I was able to page through, find the item and
>> delete it. When I paged through, the deleting was successful.
>>
>> I think that there must be a bug in the data viewer when removing data
>> found using a gql query.
>>
>> Thanks
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to