hi,
im currently working on a project that requires batch operations - eg. Batch
insert/update etc. The database im using is PostgreSQL. However, i cannot
find any documentation for batch opeartions on PostgreSQL. Does anyone know
how to do this, or if it is possible?
Thanx in advance
regards
On Mon, 2003-08-11 at 19:16, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
rbt=# ALTER USER rbt SET CONSTRAINTS ALL DEFERRED;
ERROR: syntax error at or near ALL at character 32
rbt=# ALTER USER rbt SET CONSTRAINTS = DEFERRED;
ERROR: constraints is not a recognized option
SET
rbt=3D# ALTER USER rbt SET CONSTRAINTS ALL DEFERRED;
ERROR: syntax error at or near ALL at character 32
rbt=3D# ALTER USER rbt SET CONSTRAINTS =3D DEFERRED;
ERROR: constraints is not a recognized option
SET CONSTRAINTS ALL DEFERRED is a SQL-spec-mandated command syntax.
Any similarity
Tom Lane wrote:
Shachar Shemesh [EMAIL PROTECTED] writes:
Also, I think a pretty simple workaround would be to have
PSQL search for the upper case identifier, and if not found, search for
the lower case. This should allow a migration path while the tools and
functions are being translated
Larry Rosenman wrote:
Can we modify pg_dumpall (or pg_dump?) to include a \pset pager off
to prevent the setval() calls from halting an interactive \i of the dump
file?
Your pg_dump's actually invoke the pager? Are you manually starting
psql, then doing \i dumpfile? Why would you do that
Mark Cave-Ayland said:
Hi there,
I have a RedHat 7.3 machine that can build the 7.3.4 RPMs if required -
it only contains RPMs from the vanilla CD or from updates.redhat.com.
I've just done a test build and everything seems OK except that the C
compiler is passed the -mcpu=i686 flag - I'm
What are the legal implications of copying Oracle's own PL/SQL
procedures code and porting them to PgSQL as you suggested?
Bruno BAGUETTE wrote:
Marco Roda [EMAIL PROTECTED] wrote ..
Hi,
I need to port data from an Oracle 8.0 base to PostgreSQL 7.2. I have
scripts to create the base on
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
Some notes on specific items:
Update /tmp socket files regularly to avoid their removal (Tom)
More specifically,
If you can suggest a plausible way that DROP USER is going to change the
contents of other databases (which might well contain things owned by
the target user), this might get onto the TODO list --- although I'd
personally prefer RESTRICT/CASCADE options. So far, since no one has
the
On 12 Aug 2003 at 9:58, Robert Treat wrote:
IIRC the message at the end of install used to echo out the startup
command (pg_ctl or postmaster), but now it gives some nice information
on how to get help. Should the startup message be put back in? Seems
like it is the most likely thing someone
It has been a big pleasure to me to get to know you,
and a big honor to work with you.
Do swidanie i bolshoi sbaseebo, Vadim.
Jan
--- Vadim Mikheev [EMAIL PROTECTED] wrote:
FarewellIt's time for formal acknowledgement that
I'm not in The Project any more.
I'm not interested in small
On Tue, 12 Aug 2003, Rod Taylor wrote:
world. It just seemed interesting that the numbers were three times slower
than other databases I ran it on. Here is the script which generates the
You were comparing against databases with similar safety nets to
guarantee against dataloss?
I am in
Joe,
They are done (at least the array declarations and array element
assignment part):
Way cool! How'd I miss that one?
Time to test
o Add PL/PgSQL PROCEDURES that can return multiple values
Hmmm ... I know how this got on the TODO, but it's a fragment of a larger
Tom Lane wrote:
Andreas Pflug [EMAIL PROTECTED] writes:
I wonder why you are suggesting workarounds for features that other
databases provide.
The fact that other databases provide 'em doesn't make them good ideas.
In particular, writing a trigger that assumes that only the fields
I like the sequence generator idea too.
I know Unix is bad in this area - but that's no reason for us to be bad
too. This is actually one of the (few) areas where Windows is better
than Unix. Let's go for best practice.
(new todo item Prevent automatic reuse of sysids ?)
andrew
Tom Lane
Robert Treat [EMAIL PROTECTED] writes:
IIRC the message at the end of install used to echo out the startup
command (pg_ctl or postmaster), but now it gives some nice information
on how to get help. Should the startup message be put back in?
Nothing's been removed AFAIK. Sure you're not
Tom Lane wrote:
Donald Fraser [EMAIL PROTECTED] writes:
When issuing the following type of command:
ALTER TABLE table RENAME COLUMN x TO y
The column name change is not cascading through to RULEs on a VIEW.
More specifically, INSERTs and UPDATEs contained in rules don't have
their
17 matches
Mail list logo
