My bad. I was expecting primary and unique to be mentioned here, so I did not
read on.
**INCLUDING CONSTRAINTS***
**#[https://www.postgresql.org/docs/current/sql-createtable.html#SQL-CREATETABLE-PARMS-LIKE-OPT-CONSTRAINTS]*
/*CHECK*// constraints will be copied. No distinction is made between
On 11/1/24 16:10, thi...@gelassene-pferde.biz wrote:
Adrian Klaver escribió:
On 11/1/24 13:47, Thiemo Kellner wrote:
It looks to me basically to be a "create table A as select * from B
where false".
No it more capable then that.
Yes, I wrote basically, not exactly.
CREATE TABLE LIKE h
Adrian Klaver escribió:
On 11/1/24 13:47, Thiemo Kellner wrote:
It looks to me basically to be a "create table A as select * from B
where false".
No it more capable then that.
Yes, I wrote basically, not exactly.
CREATE TABLE LIKE has like_option which
allows to transfer over more
On 11/1/24 13:47, Thiemo Kellner wrote:
It looks to me basically to be a "create table A as select * from B where
false".
No it more capable then that.
CREATE TABLE AS is bare bones, you get the
column names, types and data(or not) and that is it.
CREATE TABLE LIKE has like_option whi
It looks to me basically to be a "create table A as select * from B where
false".
01.11.2024 20:38:15 Adrian Klaver :
> On 11/1/24 12:16, thi...@gelassene-pferde.biz wrote:
>> Thanks, I shall have a look into it. I was under the assumption the the
>> create table like would create no more than
On 11/1/24 12:16, thi...@gelassene-pferde.biz wrote:
Thanks, I shall have a look into it. I was under the assumption the the
create table like would create no more than a structural copy.
Not sure what you mean by structural copy, but the table created by
CREATE TABLE LIKE will not have any as
Thanks, I shall have a look into it. I was under the assumption the
the create table like would create no more than a structural copy.
Torsten F��rtsch escribi��:
Thiemo, ��
it looks to me like you are using inheritance just to make sure
your SOURCES and TOPO_FILES tables have som
Adrian Klaver escribió:
Even if there where plans, any changes would happen in the future
and would not be help the now problem.
Yes and no. I can live without the partitioning, as I do not intend to
load data from more than one source. Other might. But until others
want to load data f
Thiemo,
it looks to me like you are using inheritance just to make sure your
SOURCES and TOPO_FILES tables have some common columns. If you are not
actually querying the TEMPLATE_TECH table and expect to see all the rows
from the other 2 tables in that one table combined, then you could use
CREATE
On 11/1/24 10:21 AM, thi...@gelassene-pferde.biz wrote:
Adrian Klaver escribió:
Changing that would count as a major change. Even if you where to
convince the developers to make the change the earliest it would
released would be with the next major release in Fall of 2025. That
assumes y
Adrian Klaver escribió:
Changing that would count as a major change. Even if you where to
convince the developers to make the change the earliest it would
released would be with the next major release in Fall of 2025. That
assumes you can convince then early enough or at all.
I was not
On 11/1/24 01:41, thi...@gelassene-pferde.biz wrote:
Adrian Klaver escribió:
It is just not the way you want to do it, see:
https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITIONING-USING-INHERITANCE
Thanks for your patience. Maybe I am not clever enough to understand
On 10/24/24 21:58, David G. Johnston wrote:
On Thursday, October 24, 2024, wrote:
Up to version 17, partitioning of tables inheriting from other
tables is not possible.
psql:../code_files/data_storage/PostgreSQL/tables/TOPO_FILES.pg_sql:68:
ERROR: no se puede crear u
Adrian Klaver escribió:
It is just not the way you want to do it, see:
https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITIONING-USING-INHERITANCE
Thanks for your patience. Maybe I am not clever enough to understand
you. I shall try to explain what I try to do.
In
On 10/25/24 11:47, Thiemo Kellner wrote:
Am 25.10.2024 um 17:57 schrieb Adrian Klaver:
I do not feel it applies to my case. I tried to create a partitioned
table that inherits columns from a base table. The documentation you
provided the URL seems to speak of realising partitioning by using
Am 25.10.2024 um 17:57 schrieb Adrian Klaver:
I do not feel it applies to my case. I tried to create a partitioned
table that inherits columns from a base table. The documentation you
provided the URL seems to speak of realising partitioning by using
inheritance.
This needs a code example
Am 25.10.2024 um 17:57 schrieb Adrian Klaver:
I do not feel it applies to my case. I tried to create a partitioned
table that inherits columns from a base table. The documentation you
provided the URL seems to speak of realising partitioning by using
inheritance.
This needs a code example
On 10/24/24 22:33, Thiemo Kellner wrote:
Thanks for taking this up.
24.10.2024 22:44:11 Adrian Klaver :
1) Have you looked at?:
https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITIONING-USING-INHERITANCE
I do not feel it applies to my case. I tried to create a partitio
On 10/24/24 12:47 PM, thi...@gelassene-pferde.biz wrote:
Hi
Up to version 17, partitioning of tables inheriting from other tables is
not possible.
psql:../code_files/data_storage/PostgreSQL/tables/TOPO_FILES.pg_sql:68: ERROR:
no se puede crear una tabla particionada como hija de herencia
Thanks for taking this up.
24.10.2024 22:44:11 Adrian Klaver :
>
> 1) Have you looked at?:
>
> https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITIONING-USING-INHERITANCE
I do not feel it applies to my case. I tried to create a partitioned table that
inherits columns from
24.10.2024 22:58:39 David G. Johnston :
>
> My impression of things is that directly using “inherit” for table creation
> is considered deprecated at this point. No one has interest in expanding on
> the feature nor even recommends it be used in new development. That
> particular unique featu
Hi
Up to version 17, partitioning of tables inheriting from other tables
is not possible.
psql:../code_files/data_storage/PostgreSQL/tables/TOPO_FILES.pg_sql:68:
ERROR: no se puede crear una tabla particionada como hija de herencia
Are there plans to support this in the future? I could not
On Thursday, October 24, 2024, wrote:
>
> Up to version 17, partitioning of tables inheriting from other tables is
> not possible.
>
>> psql:../code_files/data_storage/PostgreSQL/tables/TOPO_FILES.pg_sql:68:
>> ERROR: no se puede crear una tabla particionada como hija de herencia
>>
>
> Are ther
23 matches
Mail list logo
