On Apr 16, 5:29 pm, Craig Lucas wrote:
> Ok let me know when its available. One thing I noticed in downloading that
> branch is there are no references to "db_schema" anywhere in the code. I
> wasnt sure if that branch was supposed to contain it or not.
>
> Its also possible that I downloaded the
Ok let me know when its available. One thing I noticed in downloading that
branch is there are no references to "db_schema" anywhere in the code. I
wasnt sure if that branch was supposed to contain it or not.
Its also possible that I downloaded the wrong branch. From
https://github.com/akaariai/dj
On Apr 16, 5:07 pm, Craig Lucas wrote:
> I would be happy to test it. I just need a little guidance on how to
> implement schemas. Like do I use db_schema in the meta class, is it in the
> settings.py file? I saw some posts about setting the SCHEMA value in the
> settings.py file, but not sure tha
I would be happy to test it. I just need a little guidance on how to
implement schemas. Like do I use db_schema in the meta class, is it in the
settings.py file? I saw some posts about setting the SCHEMA value in the
settings.py file, but not sure that would work as it seems like that would
limit y
On Apr 13, 5:06 pm, Craig Lucas wrote:
> I can attempt to merge his changes in and test it. Do people typically
> merge these changes in manually? I see changes from a bunch of different
> people over the last 4 years, should I just grab the last guys changes?
The most recent work can be found fr
I can attempt to merge his changes in and test it. Do people typically
merge these changes in manually? I see changes from a bunch of different
people over the last 4 years, should I just grab the last guys changes?
On Thu, Apr 12, 2012 at 9:16 PM, Ramiro Morales wrote:
> On Thu, Apr 12, 2012 at
On Thu, Apr 12, 2012 at 9:14 PM, Craig Lucas wrote:
> i actually didnt try the db_column attribute because I read about quoting it
> before I started writing the code. But that wont solve the schema problem.
> It will still try to create the index and fk constraints with the dots and
> quotes aro
i actually didnt try the db_column attribute because I read about quoting
it before I started writing the code. But that wont solve the schema
problem. It will still try to create the index and fk constraints with the
dots and quotes around the table name.
i believe it is required to quote the sc
On Thu, Apr 12, 2012 at 3:06 PM, Craig Lucas wrote:
> i have developed a database for a client that uses camel casing in the
> database. we are now trying to get a models.py file to mimic the
> database structure and i have run into a few bugs with regards to
> using quoted table names.
>
> The fi
i have developed a database for a client that uses camel casing in the
database. we are now trying to get a models.py file to mimic the
database structure and i have run into a few bugs with regards to
using quoted table names.
The first issue is when you specify a foreign key field it takes the
t
10 matches
Mail list logo
