Seb <[EMAIL PROTECTED]> writes:
> But the problem still occurs with 'psql -f INPUTFILE', where tab
> complete is irrelevant, so I'm confused.
You sure? I can't make the example fail that way. It does fail
when the example-with-tab is cut and pasted directly into a terminal
window, which is exact
On Sun, 23 Mar 2008 18:15:55 -0700,
"Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
[...]
> Actually that would make sense as psql supports tab complete so if the
> terminal interprets a tab, it isn't going to treat it as spaces. I
> would suggest changing your editor to treat tabs as 4 spaces.
But
On Sun, 23 Mar 2008 20:01:28 -0500
Seb <[EMAIL PROTECTED]> wrote:
> Thanks Joshua, that is the problem I wanted to illustrate; i.e.
> whenever a tab separates the field name from the data type spec, the
> tab character gets swallowed and psql cannot parse correctly. So it
> seems tabs are not int
On Sun, 23 Mar 2008 17:48:09 -0700,
"Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
[...]
> I can not duplicate your problem. However when I copy and paste
> directly from your email it does indeed fail watch:
[...]
> That is a direct copy and paste from your email. Notice that there is
> no space
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 23 Mar 2008 19:35:46 -0500
Seb <[EMAIL PROTECTED]> wrote:
> CREATE TABLE test
> (
> idInt8,
> phenotype Varchar(510),
> genotype Varchar(510)
> );
serial_test=# CREATE TABLE test
(
id Int8,
phenotype Varchar
Hi,
I'm fairly new to postgresql, and I'm having some problems understanding
the syntax of SQL statements in psql. According to the documentation,
white space can be used freely. However, the following fails:
CREATE TABLE test
(
id Int8,
phenotype Varchar(510),
genotype Varchar