From: | Christian Rudow <Christian(dot)Rudow(at)thinx(dot)ch> |
---|---|
To: | John Huttley <john(at)mwk(dot)co(dot)nz>, PostgreSQL General <pgsql-general(at)hub(dot)org> |
Subject: | Re: [GENERAL] Limitation |
Date: | 1999-06-24 05:49:11 |
Message-ID: | 3771C6D7.52E81F4F@thinx.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
John Huttley wrote:
> PG cannot handle this. see below.
>
> create view product as
> Select code As Stock_Code,
> Substr(Code,1,1) As Process_ID,
> Substr(Code,2,2) As SubProcess_ID,
> Substr(Code,4,1) As SubStrate_ID,
> Substr(Code,5,2) As Length_ID,
> Substr(Code,7,2) As Width_ID,
> Substr(Code,9,2) As Thickness_ID,
> Substr(Code,11,3) As Face_ID,
> Substr(Code,14,1) As Facefinish_ID,
> Substr(Code,15,3) As Back_ID
> -- Substr(Code,18,1) As Backfinish_ID
> >From INMASTER;
> ERROR: DefineQueryRewrite: rule plan string too big.
John,
I generate a lot of sql create scripts from perl classes.
These scripts tend to hav a lot of whitespaces that make them beautiful
to read.
But just for me ... that's what PG means to this :
PQsendQuery() -- query is too long. Maximum length is 8191
So far, I got along very well just stripping unneeded whitespaces out of
the scripts before i run them.
Probably a simple s/^ // would already help in your case.
Chris
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Christian Rudow E-Mail: Christian(dot)Rudow(at)thinx(dot)ch
ThinX networked business services Stahlrain 10, CH-5200 Brugg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Rudow | 1999-06-24 06:02:00 | Re: [GENERAL] Date time insertion |
Previous Message | John Huttley | 1999-06-24 04:44:12 | Limitation |