Yes, the essence of what you describe below is what I plan to do - what a pain, though.
It's a pity that the dev app server doesn't look at the automatically- generated indices at launch-time, but I'll live with it. On Jul 1, 8:22 am, Cyrille Vincey <[email protected]> wrote: > Yes, I have noticed the same behaviour. > My workaround: once a index has been automatically generated, I copy > its xml configuration from "datastore-indexes-auto.xml" to "datastore- > indexes.xml". > Thus I consider "datastore-indexes-auto.xml" as automatic > propositions. > > On Jun 30, 12:14 pm, Ian Marshall <[email protected]> wrote: > > > > > > > > > I have my datastore-indexes.xml configuration file set as > > > <datastore-indexes autoGenerate="true"> > > </datastore-indexes> > > > I make successive runs of the development server. Each time before > > stopping it, I wait a couple of minutes for updates to be flushed to > > local_db.bin and datastore-indexes-auto.xml. > > > I have found that successive runs of the development server can cause > > previously-existing automatically-generated datastore indices to be > > erased (even though the datastore data in local_db.bin is preserved). > > > Has anyone else found this? Is this expected behaviour or a glitch? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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/google-appengine-java?hl=en.
