On Tuesday 29 November 2005 17:01, Leif B. Kristensen wrote:
>Is there an easy and non-disruptive way to do this?
For the record, I just did the following:
pgslekt=> create table rel_cits (
pgslekt(> relation_fk integer references relations (relation_id),
pgslekt(> source_fk integer references so
On Tuesday 29 November 2005 15:52, Leif B. Kristensen wrote:
>Uh-oh. That's my first 'gotcha' in PostgreSQL.
>
>I added the following constraints:
I probably should drop both the inheritance and the citation_id
altogether, and operate with two separate tables:
CREATE TABLE relation_citations (
On Tuesday 29 November 2005 15:43, A. Kretschmer wrote:
>> I got an error when I transferred the data to my Web database
>> running MySQL:
>
>MySQL is a other RDBMS. You can't expect that all features from
>PostgreSQL are working with MySQL.
>
>> ERROR 1062 at line 19839 in file: 'ss_relation_citat
On Tuesday 29 November 2005 15:37, Tom Lane wrote:
>relation_citations doesn't have a primary key. See
>http://www.postgresql.org/docs/8.1/static/ddl-inherit.html
>particularly the "caveats" section.
Uh-oh. That's my first 'gotcha' in PostgreSQL.
I added the following constraints:
ALTER TABLE r
am 29.11.2005, um 15:31:30 +0100 mailte Leif B. Kristensen folgendes:
> CREATE TABLE citations (
> citation_id INTEGER PRIMARY KEY,
> source_fk INTEGER REFERENCES sources (source_id)
> );
>
> CREATE TABLE relation_citations (
> relation_fk INTEGER REFERENCES
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
> I just noticed that I accidentally got a duplicate id. My
> definitions are here:
> CREATE TABLE citations (
> citation_id INTEGER PRIMARY KEY,
> source_fk INTEGER REFERENCES sources (source_id)
> );
> CREATE TABLE relat
