I actually I just found the problem; the tables are in fact created in the
right order - the problem is that the DDL contains INHERITS ( "parent" ).
It gives the same error if I try to run the code in a GUI with the
inherited table name quoted, without (the quoting) though it works.
On Mon, Nov
I attached a script that reproduces the problem. It actually only happens
if the metadata contains a schema, then the tablename in the INHERITS()
clause get quoted, which causes the problem.
On Monday, November 23, 2015 at 7:13:27 PM UTC+1, Adrian wrote:
>
> I actually I just found the problem;
On 11/23/2015 03:15 PM, Adrian wrote:
> I attached a script that reproduces the problem. It actually only
> happens if the metadata contains a schema, then the tablename in the
> INHERITS() clause get quoted, which causes the problem.
>
postgresql_inherits was only added in 1.0.How can
That's true now that you are saying it, I actually implemented it myself
before using a simple @compiles with CreateTable.
On Mon, Nov 23, 2015 at 9:33 PM Mike Bayer wrote:
>
>
> On 11/23/2015 03:15 PM, Adrian wrote:
> > I attached a script that reproduces the problem.
On 11/23/2015 03:15 PM, Adrian wrote:
> I attached a script that reproduces the problem. It actually only
> happens if the metadata contains a schema, then the tablename in the
> INHERITS() clause get quoted, which causes the problem.
anyway, there's no direct "postgresql_inherits_schema"
Hello,
I have the following problem - I recently upgraded to the 1.0+ branch from
0.9 and now the PostgreSQL table inheritance does not work properly any
longer because the tables that inherit from the master table are sometimes
created before (random) the actual table they inherit from,
On 11/23/2015 12:43 PM, Adrian wrote:
> Hello,
>
> I have the following problem - I recently upgraded to the 1.0+ branch
> from 0.9 and now the PostgreSQL table inheritance does not work properly
> any longer because the tables that inherit from the master table are
> sometimes created before
That works and solves it, thanks!
On Mon, Nov 23, 2015 at 9:37 PM Mike Bayer wrote:
>
>
> On 11/23/2015 03:15 PM, Adrian wrote:
> > I attached a script that reproduces the problem. It actually only
> > happens if the metadata contains a schema, then the tablename in