Re: truncated string problem

From: Eric Clark <eclark(at)zerohp(dot)com>
To: Rob Brown-Bayliss <rob(at)zoism(dot)org>
Cc: PostgreSQL General List <pgsql-general(at)postgresql(dot)org>, Pypgsql List <pypgsql-users(at)lists(dot)sourceforge(dot)net>
Subject: Re: truncated string problem
Date: 2003-07-29 20:46:36
Message-ID: 1059511597.10852.4.camel@eric
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 2003-07-29 at 13:38, Rob Brown-Bayliss wrote:
>
> Hi, Running the following SQL via pypgsql:
>
> INSERT INTO "songs" ("p_key", "title", "artist", "date", "album",
> "tracknumber", "time", "file") VALUES
> ("ea0e89f596619af1837f424c0767ffd9", "Sugar Mountain", "Neil Young",
> "1979", "Live Rust", "1", "302.226666667",
> "/oggs/Neil_Young-Sugar_Mountain.ogg");

Double quotes are reserved for identifier's like table and column
names. You should use single quotes's for your values. phpPgAdmin is
probably rewriting your statement.

Eric

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Freddy Menjívar M. 2003-07-29 20:47:37 Re: Does the block of code in a stored procedure execute as a transaction?
Previous Message Rob Brown-Bayliss 2003-07-29 20:38:47 truncated string problem