Hi,
I think support for postgres schema's is coming in 1.3 but I wonder is it
possible to support schema in 1.2.1? If it can - could someone provide the
how? or maybe a link.
Thanks in advance,
Johnf
--
You received this message because you are subscribed to the Google Groups
"Django users"
On Sun, 15 Nov 2009 15:20:32 -0800, Christophe Pettus
wrote:
> On Nov 15, 2009, at 2:35 PM, Melvyn Sopacua wrote:
>> Is it possible for a "Django appointments application" to understand
>> and use
>> the geographical information from the tables in the geo_regionX
>> schema and
>> equally impor
On Nov 15, 2009, at 2:35 PM, Melvyn Sopacua wrote:
> Is it possible for a "Django appointments application" to understand
> and use
> the geographical information from the tables in the geo_regionX
> schema and
> equally important to treat that specific schema as read only, as the
> data is
Hi,
I'm considering Django for some projects, but initial research on schema
support only showed some generics and I can't really find a good answer to my
specific situation. So, I figured I'd try here.
I've developed a database which should support various applications, se
. I noticed Django doesn't have any
> explicit schema support, but instead uses app prefixes. I realize that
> some would argue that's functionally equivalent. But not when you're
> looking at all those tables in pgAdmin.
>
> Would it be difficult to add schema suppor
t exposed to all applications and tables within a
>> database. I usually segregate the tables into schemas based on their
>> relationship to one another. With several hundred tables in the
>> database, this gets pretty critical. I noticed Django doesn't have any
>> exp
"public" schema except for
> things I want exposed to all applications and tables within a
> database. I usually segregate the tables into schemas based on their
> relationship to one another. With several hundred tables in the
> database, this gets pretty critical. I noticed
cept for
> things I want exposed to all applications and tables within a
> database. I usually segregate the tables into schemas based on their
> relationship to one another. With several hundred tables in the
> database, this gets pretty critical. I noticed Django doesn't have any
this gets pretty critical. I noticed Django doesn't have any
explicit schema support, but instead uses app prefixes. I realize that
some would argue that's functionally equivalent. But not when you're
looking at all those tables in pgAdmin.
Would it be difficult to add schema su
On 06-Jan-07, at 12:56 AM, Christoph Haas wrote:
I'd like to hear comments. Or is PostgreSQL an uncommon DBMS to use
with Django? (btw, is there a reason to prefer psycopg over
psycopg2?) I can of course restrain myself to the "public" schema
but my application would benefit from differen
On 1/6/07, Christoph Haas <[EMAIL PROTECTED]> wrote:
The problem has been raised in
- http://code.djangoproject.com/ticket/1051
Did anyone else find a workaround? Is it meanwhile possible to use at least
a models.py without using "inspectdb"? My experiments
with 'schemaname.tablename' just l
Dear list...
I'm currently starting a larger project and want to use Django for it.
First order of business was creating the necessary database schema with
pgadmin3 (a PostgreSQL GUI). Next thing after setting my settings.py right
was to run "django-admin inspectdb" to get my already existing
12 matches
Mail list logo
