Hi Russ,
thanks, that's what I'm using currently. Not optimal but I guess it'll
have to do.
On Jun 26, 12:42 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Wed, Jun 25, 2008 at 11:54 PM, [EMAIL PROTECTED]
>
> <[EMAIL PROTECTED]> wrote:
>
> > Hi everyone,
>
> > I'm working on a projec
On Wed, Jun 25, 2008 at 11:54 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Hi everyone,
>
> I'm working on a project that has a very solid database design but
> many of the used features aren't supported by Django (for example,
> multiple column primary keys).
>
> The project has a complet
Hi,
nope, model names match to the database but, for example, I haven't
found a way to be able to create a pgsql function inside a custom
script so some stuff, queries that invoke functions (stored
procedures), cannot be tested. Also, given that the database SQL
script is versioned, I'd really li
i think i understand what youre saying?
by test database, you mean you want to test django out but your
declared models names dont match your db?
there is a meta option for db table
http://www.djangoproject.com/documentation/model-api/#db-table
On Jun 25, 11:54 am, "[EMAIL PROTECTED]" <[EMAIL
Hi everyone,
I'm working on a project that has a very solid database design but
many of the used features aren't supported by Django (for example,
multiple column primary keys).
The project has a complete database creation script but I haven't
found a way to use it to create the test database wh
5 matches
Mail list logo