On 9/12/13 6:44 AM, Sayth Renshaw wrote:
On Thursday, September 12, 2013, Germán Larraín wrote:
Some comments:
* why use sqlalchemy if Django has its own ORM?
* you mentioned parsing SQL entries; watch out!
* if you are starting a new project, I seriously recommend you to
use PostreSQL, not MySQL/Maria DB
+1
I was just googling for methods and examples of how people do this. Of
the very scarce info out there Sqlalchemy was in it.
That would be a red herring.
In the django docs it has initial fixtures.
https://docs.djangoproject.com/en/1.2/howto/initial-data/#providing-initial-data-with-fixtures
But this doesn't seem to provide the functionality of loading
recurring data via XML data thru ORM to database.
I would write a python script to stuff it in to the database directly or
if you want others to be able to upload files to be read in then
integrate an upload capability with some backend python code. If the
files are large then you will want to have a separate thread do the
work. And if the files need validation you may want to break this into
two pieces so the file is uploaded and the file name is stashed in a
model, then another thread or cron job can pick it up and do some
processing, maybe keeping track of the status in the database also.
For a separate python script you may need to write some simple SQL, but
for the django portions you would not need to touch that.
Write your models for the dataflow you need, then fill in the other
pieces with some code.
hth
- Tom
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.
