From: Kristian Köhntopp <kk@shonline.de>
To: Oliver Duke-Williams <oduke@gisca.adelaide.edu.au>
Cc: pgsql-sql@postgresql.org
Cc: phplib@mail.shonline.de
Subject: Re: [PHPLIB] SQL probs with phplib
Date: Mon, 14 Sep 1998 11:28:17 +0200
Message-ID: <35FCE1B1.49CB7635@shonline.de> (raw)
References: <9809141757.ZM3032@tsg109.gisca.adelaide.edu.au>
Oliver Duke-Williams wrote:
> changed varchar(14) DEFAULT '' NOT NULL,
> ERROR: type name lookup of changed failed
changed is a regular varchar(14) and should be taken by Postgres without
problems. At least my Postgres did.
> ERROR: parser: Syntax error at or near "k_username"
Just don´t name that key (leave out the k_username). Alternatively
define the table without keys first and add the keys later using the
CREATE INDEX statement.
> Having drawn a blank in searching list archives, I'd be grateful
> for any advice about what the correct pgsql versions of the above
> should be.
Postgres support is new in release-5 of PHPLIB. There are not many
success reports with Postgres up to now. I am a MySQL type myself and
very new to Postgres...
Kristian
--
SH Online Dienst GmbH, Kristian Koehntopp,
Siemenswall, 24107 Kiel, +49 431 386 436 00
Using PHP3? See our web development library at
http://phplib.shonline.de/ (GPL)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: kk@shonline.de, oduke@gisca.adelaide.edu.au, phplib@mail.shonline.de
Subject: Re: [PHPLIB] SQL probs with phplib
In-Reply-To: <35FCE1B1.49CB7635@shonline.de>
References: <9809141757.ZM3032@tsg109.gisca.adelaide.edu.au> <35FCE1B1.49CB7635@shonline.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox