I'm pretty new to GAE, but I did search for the answer to this.
Unfortunately, if you fail to search for the proper terminology, it's
the same as failing to search. :o)

Normally, when writing a web application in PHP or .NET, I would write
SQL scripts to create the DB/users/permissions, one to create tables,
one to create views and/or stored procedures, and one to preload the
database with initial data. It's the last script that I'm struggling
to figure out the proper way to do in GAE.

So, for example, let's say I have a table that contains user types
(Admin, Author, Editor....etc.) to be used in a drop down when
creating a new user. I _could_ just hardcode these values into a
template, but I don't want to do that. I _could_ create a form to
manually input these into the data store, but I don't want to do that
either (since it will likely be rare occurrence).

My only option that I'm aware of is to create some Python code that
creates these objects and writes them to the data store. Essentially,
I have a password protected web page called "preloaddata" that, when
called, will dump all the data from the data store, create new objects
with the initial data, and write it to the database.

This is just an example, so if there's a reason why I should preload
the data for this particular instance, please disregard that and
pretend it's a viable option. I'm really looking for what the proper
GAE way to preload data into the data store is without using a form or
statically writing all the data in Python code.

I appreciate any help anyone can offer. I'm really just looking for
the GAE equivalent to a database script to enter data.

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 [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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to