Am Donnerstag, den 18.08.2005, 15:52 -0500 schrieb Adrian Holovaty: > On 8/18/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I'm in the process of doing this myself. I'm porting a job monitoring > > system to django. It was written in python before, but the web front > > end was written in PHP. Seems to be going well so far. I have the model > > and can access the APIs. I've come across some issues, but am new to > > django, so am working through them before anything else. > > Very cool, Tom. Please do let us know how we can improve the "Using > existing databases" documentation if you have any suggestions.
Well, one question that has been left open, how does it work with database models, that use oid as primary key, and what about tables that have compound (multiple columns) primary keys? And there is completely another answer that would match with the question: How to write a completely "independant" model -> which APIs must be implemented by a model. (Consider "legacy databases" that are no SQL databases.) Andreas
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
