pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feed(no subject)
2+ messages / 2 participants
[nested] [flat]
* (no subject)
@ 2003-10-28 05:45 Cobus Carstens <cobus.carstens@swistgroup.com>
2003-10-31 09:58 ` Re: Michael Meskes <meskes@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: Cobus Carstens @ 2003-10-28 05:45 UTC (permalink / raw)
To: pgsql-interfaces
Hi there.
I'm running Postgresql 7.3.2 on Mandrake 9.1.
I'm using ecpg (version 2.10.0) to compile the embedded sql code in my C
programs.
The problem experienced has to do with array indexing in SQL statements.
I browsed your test files in the CVS repository and found one
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/interfaces/
ecpg/test/test1.pgc?rev=1.31.2.1&content-type=text/x-cvsweb-markup) that
contains the code I would like to be able to use.
When I precompile the abovementioned file with ecpg, I get the following
error
test1.pgc:130: parse error at or near "[".
It is the same problem I'm experiencing with my program. I tested my
program on Postgresql 7.3.4 as well, but it also did not work (the ecpg
version was the same as the 7.3.2's).
What do you suggest I do to get this working? Grab latest code from CVS?
My second question is with regards to Oracle style bulk inserts/updates.
I've played around with the "COPY" command and it seems to have good
performance (even though I have to explicitly sprintf all values in a
string first). I'm currently working on a port of existing software that
stores huge amounts of (telecoms) data, so performance is critical. Is
there any special way of handling a lot of updates? I can understand
that updates might need to be done one at a time, but it would be nice
if I can cut out the overhead of calling an update sql statement
repeatedly - I'm thinking in the line of the Oracle bulk updates where
you give the sql statement and host arrays containing the fieldvalues
for the different updates.
Any hints/suggestions would be appreciated.
Regards,
Cobus Carstens
Attachments:
[application/x-pkcs7-signature] smime.p7s (4.0K, ../../DEC925D2FB9081448C3D6EC26E85868CF81404@steinmail.swistgroup.com/2-smime.p7s)
download
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re:
2003-10-28 05:45 (no subject) Cobus Carstens <cobus.carstens@swistgroup.com>
@ 2003-10-31 09:58 ` Michael Meskes <meskes@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Michael Meskes @ 2003-10-31 09:58 UTC (permalink / raw)
To: Cobus Carstens <cobus.carstens@swistgroup.com>; +Cc: pgsql-interfaces
On Tue, Oct 28, 2003 at 07:45:42AM +0200, Cobus Carstens wrote:
> I'm running Postgresql 7.3.2 on Mandrake 9.1.
> I'm using ecpg (version 2.10.0) to compile the embedded sql code in my C
> programs.
>
> The problem experienced has to do with array indexing in SQL statements.
> I browsed your test files in the CVS repository and found one
> (http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/interfaces/
> ecpg/test/test1.pgc?rev=1.31.2.1&content-type=text/x-cvsweb-markup) that
> contains the code I would like to be able to use.
>
> When I precompile the abovementioned file with ecpg, I get the following
> error
> test1.pgc:130: parse error at or near "[".
The syntax used in test1.pgc in CVS is only supported in ecpg 3.0.0
coming with PostgreSQL 7.4. If you want to use the older version check
for an older version of test1.pgc.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2003-10-31 09:58 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-10-28 05:45 Cobus Carstens <cobus.carstens@swistgroup.com>
2003-10-31 09:58 ` Re: Michael Meskes <meskes@postgresql.org>
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