Yes - the trick is with slow odbc interfaces is to differentiate
between auto-increment/log style source tables and those which may
update any record. Also try and pick your tables and fields to sync
judiciously and work out your sync cycle based on how expensive in
time it is to retrieve all the records from the source table. I use a
strategy of updating some hourly and more expensive tables with
millions of records once a week. If you are feeding a web database
offsite then hash your records and store in sqlite so that you can
compare and only send changes to the django database. Basically you
just store the primary key and the hash in the sqlite table with the
same name as your destination table. I thought hashing and comparing
records would be slow but once you tune sqlite correctly that is
insignificant compared to actually reading the records from slow odbc
interfaces.


On Sep 12, 5:12 pm, Jarek Zgoda <[EMAIL PROTECTED]> wrote:
> Wiadomość napisana w dniu 2008-09-11, o godz. 22:50, przez Jason Sypolt:
>
> > Is it possible to connect to an as400 database using django
> > (preferably) or with python? I would like to build a product catalog
> > site using django and read in products and send orders to the as400.
>
> DB2/400 is accessible using ODBC. If there is any database backend  
> that uses ODBC for connecting to databases, you are set.
>
> But I had much more success with other databases, feeded with data  
> from DB2/400. This database is optimized for sequential access and set  
> operations (via SQL interface) can be really slow.
>
> --
> We read Knuth so you don't have to. - Tim Peters
>
> Jarek Zgoda, R&D, Redefine
> [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to