back on this thread.
I have a new setup now and back into development, of course without that old
datastore (which had just sample/test data, so no issues).
Regards,
R.Rajkumar
On Wed, Jun 24, 2009 at 4:51 PM, Nick Johnson (Google) <
nick.john...@google.com> wrote:
> Hi rraj,
>
No, but I gave a different datastore location (using datastore_path and
history_path, as shown in the trace snippet) which I thought was equivalent
enough - is it not ?!
Regards,
R.Rajkumar
On Tue, Jun 23, 2009 at 4:17 PM, Nick Johnson (Google) <
nick.john...@google.com> wrote:
>
Hi,
Had anybody encountered the following error and can guide me on how you
fixed it ?
When running the development app server, initial run throws
"SystemError: frexp() result out of range"...
C:\Program Files\Google\google_appengine>dev_appserver.py
--datastore_path=C:\gae_data --history_path=C:
Yes, I have read them and had even tried the vacuum_indexes procedure. It
did not work, as I had mentioned in my mail.
Tried it again today and they got deleted at once from my indexes.
By the way, the problem is not related to exploding indexes - there were 3
new indexes of 2 to 3 properties eac
Hi,
I have an app ("matrimonyplanner") which has 3 indexes stuck in "Error"
state.
Tried the vacuum_indexes procedure, so as to upload them again, but it does
not go into "Deleting" state and remains in "Error".
Any tips on how to proceed ?
Regards,
Rajkumar
On Tue, Nov 11, 2008 at 10:16 PM, M
