Stephan Szabo <[EMAIL PROTECTED]> writes:
> Well, technically by SQL92 I believe the second query should be an error
> since the table reference "bar b" should not be exporting the name "bar"
> unless I'm misreading the spec...
Correct. SQL sez that "FROM bar b" exposes the correlation name "b",
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The problem I am encountering is with having a primary key labeled as
> serial. Do I have to drop the sequence also to be able to recreate the
> table? Omitting the sequence drop did not seem to allow the creation of the
> table with a serial, but
Bill Barnes wrote:
>
> Oh, if only I could be so sanguine about my learning curve in matters of
> Linux, PostgreSQL, Enhydra, Glade, gnome-db, bonobo, HTML, XML, DHCP, NIS,
> NSF, DNS, ABC, XYZ, ETC, ETC, ETC.
>
> Bill
:-)
It's like I told a client about learning PHP (which I had had little
ex
Oh, if only I could be so sanguine about my learning curve in matters of
Linux, PostgreSQL, Enhydra, Glade, gnome-db, bonobo, HTML, XML, DHCP, NIS,
NSF, DNS, ABC, XYZ, ETC, ETC, ETC.
Bill
>= Original Message From Lamar Owen <[EMAIL PROTECTED]> =
>Tom Lane wrote:
>> Lamar Owen <[EMAIL PRO
Thanks, that makes sense.
Although, I'd much rather have an error then the wrong data. :(
Cheers,
Darrin
>From: Stephan Szabo <[EMAIL PROTECTED]>
>To: Darrin Ladd <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED]
>Subject: Re: [GENERAL] Table Alias
>Date: Tue, 29 Aug 2000 17:48:57 -0700 (PDT)
>
>
>O
I'm also having a problem with my references.
In the script below, I get this error after each references statement:
NOTICE: CREATE TABLE/FOREIGN KEY clause ignored; not yet implemented
Any ideas?
drop table model_part;
drop table models;
drop table parts;
drop table category;
drop sequence m
Oh wow (after reading over pg_dump and trying it). I didn't know about
that. That's very nice.
Is it safe and accurate? Should I be able to feel mostly secure about using
that to dump my database definitions?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
- Original Message
Hi all,
I am trying to figure out how much work is involved in migrating an
existing mysql database and web/command-line perl interface to postgres.
I got some scripts hacked together that can translate the mysql schema and
data dump ok, but I ran into a
ERROR: parser: parse error at or near
> here is the vacuum verbose :
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
> We have lost the connection to the backend, so further processing is
impossible. Termina
The problem I am encountering is with having a primary key labeled as
serial. Do I have to drop the sequence also to be able to recreate the
table? Omitting the sequence drop did not seem to allow the creation of the
table with a serial, but when I added a drop sequence, the table cr
ok Hermit Hacker
here is the vacuum verbose :
mydb=> vacuum verbose ;
NOTICE: --Relation pg_type--
NOTICE: Pages 2: Changed 0, Reapped 1, Empty 0, New 0; Tup 142: Vac 0, Keep/VTL 0/0,
Crash 0, UnUsed 2, MinLen 105, MaxLen 109; Re-using: Free/Avail. Space 256/0;
EndEmpty/Avail. Pages 0/0. El
[EMAIL PROTECTED] (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> You can always stick to Postgres 6.5 :-). There are certain features
>> that just cannot be added without redoing the on-disk table format.
>> I don't think we will ever want to promise
Tom Lane <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> > Will there be a clean upgrade path this time, or
> > yet another dump-initdb-restore procedure?
>
> Still TBD, I think --- right now pg_upgrade would still work, but if
> Vadim finish
> From: "Matthew Kennedy" <[EMAIL PROTECTED]>
> > I have a ton of data in a text delimited file from an old legacy system.
> > When uploading it into postgres, I'd do something like this:
> >
> > COPY stuff FROM 'stuff.txt' USING DELIMITERS = '|';
> >
> > The problem is some of the rows in stuff.t
[EMAIL PROTECTED] (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> Will there be a clean upgrade path this time, or
> yet another dump-initdb-restore procedure?
Still TBD, I think --- right now pg_upgrade would still work, but if
Vadim finishes WAL there's going to have to be a dump/reload f
I'm building a database and making my table creates in a text file so that,
if I want to recreate my database, I can just rerun the scripts.
At the top of the script are the statements to drop the tables. Next is the
area which creates the tables.
The problem I am encountering is with having a
Well, you could always make a table that has no constraints on duplicates
and COPY TO that one. Then, make a query that inserts the data into your
production table that handles the duplicates.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
- Original Message -
From: "Matth
On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsrød wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
>
> > On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsr d wrote:
> >
> > > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > >
> > > > On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsr d w
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsr d wrote:
>
> > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> >
> > > On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsr d wrote:
> > >
> > > > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > >
On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsrød wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
>
> > On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsr d wrote:
> >
> > > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > >
> > > > On Mon, 28 Aug 2000, Miguel Omar Carvajal wrote:
> >
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> On Mon, 28 Aug 2000, Miguel Omar Carvajal wrote:
>
> > Hi there,
> >When will Postgresql 7.1 be released?
>
> right now, we're looking at October-ish for going beta, so most likely
> November-ish for a release ...
Will there be a clean upgrad
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsr d wrote:
>
> > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> >
> > > On Mon, 28 Aug 2000, Miguel Omar Carvajal wrote:
> > >
> > > > Hi there,
> > > >When will Postgresql 7.1 be released?
> >
I have a ton of data in a text delimited file from an old legacy system.
When uploading it into postgres, I'd do something like this:
COPY stuff FROM 'stuff.txt' USING DELIMITERS = '|';
The problem is some of the rows in stuff.txt may not conform to the
stuff table attributes (duplicate
On 29 Aug 2000, Trond Eivind [iso-8859-1] Glomsrød wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
>
> > On Mon, 28 Aug 2000, Miguel Omar Carvajal wrote:
> >
> > > Hi there,
> > >When will Postgresql 7.1 be released?
> >
> > right now, we're looking at October-ish for going beta, so
try 'vacuum verbose;' ... if that doesn't work, try doing a pg_dump/reload
... and, above all ... upgrade to v7.x as soon as possible ...
On Tue, 29 Aug 2000, Ange Michel POZZO wrote:
> hi all,
>
> i use [PostgreSQL 6.5.2 on i686-pc-linux-gnu, compiled by gcc 2.95.2] on a
> linux mandrake 7.0
Darrin Ladd wrote:
>
> Ok, so I'm an idiot...sorry.
>
> While running the *correct* rpm (SRPM: postgresql-7_0_2-1_src.rpm), it keeps
> failing. It appears to be trying to implement the python interface, but the
> required config directory with the make file is missing off the file system.
>
26 matches
Mail list logo
