On Monday 13 December 2004 08:15 am, Tom Lane wrote:
>
> One character per character, whether that be a visible character or
> whitespace (including newlines). Collapsing out whitespace is
> definitely not going to give you the right count.
and while on this topic, how does one interpret the line
Would you please test 8.0RC release on the ftp site. It might already
be fixed.
---
Christoph Haller wrote:
> I doubt this is the right list, but it's the only one I'm subscribed to,
>
> so please, if one of the core membe
Alex Beamish <[EMAIL PROTECTED]> writes:
> I'm getting a frustrating error
> ERROR: parser: parse error at or near "(" at character 201
> in a CREATE TABLE statement from an SQL script that I'm running from
> within a Perl script. When I run the same script from the command
> line, either as a r
On Thu, Dec 09, 2004 at 03:19:56PM -0500, Alex Beamish wrote:
> I'm getting a frustrating error
>
> ERROR: parser: parse error at or near "(" at character 201
>
> in a CREATE TABLE statement from an SQL script that I'm running from
> within a Perl script. When I run the same script from the c
On Mon, Dec 06, 2004 at 06:58:43PM -0800, Mian Yong Leow wrote:
> I perform an INSERTion and there weren't any complains
> of error, so i assume that it has no error. When i
> perform a SELECT there were 0 rows in the table.
What language or program are you using to do the inserts? How are
you
Hi,
I'm getting a frustrating error
ERROR: parser: parse error at or near "(" at character 201
in a CREATE TABLE statement from an SQL script that I'm running from
within a Perl script. When I run the same script from the command
line, either as a regular user or as root, it works fine.
The
Has anyone encountered this problem before?
I perform an INSERTion and there weren't any complains
of error, so i assume that it has no error. When i
perform a SELECT there were 0 rows in the table.
This is just a simple table with (Integer,
Varchar(25),Varchar(50),Varchar(50)) type of data.
Th
