On Sat, Jul 29, 2017 at 3:38 PM, tel medola wrote:
> Depends.
> When you create your tables in new schema, the script was the same from
> "qa"?
> Sequences, tables, etc.. belong to the schema where was created.
>
> Roberto.
>
> Em sáb, 29 de jul de 2017 às 16:17, marcelo
> escreveu:
>
>> Some da
Depends.
When you create your tables in new schema, the script was the same from
"qa"?
Sequences, tables, etc.. belong to the schema where was created.
Roberto.
Em sáb, 29 de jul de 2017 às 16:17, marcelo
escreveu:
> Some days ago I asked regarding tables located in different schemas.
> Now, my
Some days ago I asked regarding tables located in different schemas.
Now, my question is
Suppose I have two schemas (other than public): "qa" and "production".
Initially I create all my tables in "qa". All of them have a primary key
of type serial.
Later, I will copy the tables definitions to pr
Thank you, Tom!
Should I have the CHECK in the new table written out again as in -
On Sat, Jul 29, 2017 at 3:41 PM, Tom Lane wrote:
>
> You have to use the separate-constraint FK syntax:
>
> CREATE TABLE words_payments (
> sid textNOT NULL,
> social integer NOT N
Alexander Farber writes:
> Unfortunately, I get the error:
> ERROR: 42830: number of referencing and referenced columns for foreign key
> disagree
> How to refer to the (sid, social) FKs properly please?
You have to use the separate-constraint FK syntax:
CREATE TABLE words_payments (
s
Good afternoon,
in 9.5.7 I have the following 2 tables -
CREATE TABLE words_users (
uid SERIAL PRIMARY KEY,
created timestamptz NOT NULL,
visited timestamptz NOT NULL,
ip inetNOT NULL,
fcm text,
apnstext,
sns t
Hello,
Is there a way to have access to the tzdata boundaries from within postgres
?
the zdump linux command gives something like
--
zdump -v /usr/share/zoneinfo/America/Los_Angeles | grep 2017
Sun Mar 12 09:59:59 2017 UTC = Sun Mar 12 01:59:59 2017 PST isdst=0
gmtoff=-28800
Sun Mar 12 10:0
