Simple script:
CREATE TABLE test(a int);
\copy test from '/tmp/wow'
select * from test;
now produce error:
\copy: COPY state must be terminated first
I missed something?
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'k
I have a large customer who is converting from informix to postgres and
they have made extensive use of
update table set (col...) = ( val...)
as a first pass would it be possible to translate this in the parser to
update table set col=val
It would appear that this is SQL3 compliant
::=
Bruce Momjian wrote:
>
> I have a new idea. You know how we have search_path where you can
> specify multiple schema names. What if we allow the config_dirs/-C to
> specify multiple directories to search for config files. That way, we
> can use only one variable, and we can allow people to plac
Bruce,
Can you chime in with your support here?
Dave
I have a large customer who is converting from informix to postgres and
they have made extensive use of
update table set (col...) = ( val...)
as a first pass would it be possible to translate this in the parser to
update table set col=val
I just compiled pgsql version 7.3.2 in a redhat 7.3 workstation and I
get this error when I run psql:
psql: /lib/i686/libc.so.6: version `GLIBC_2.3' not found (required by
psql)
I have to update glibc? How? No rpms are avaliable, how the configure
script haven't detected this problem?
Dave Cramer <[EMAIL PROTECTED]> writes:
> It would appear that this is SQL3 compliant
> ::=
>
> ::=
>
> |
I see no parentheses allowed there in the SQL99 spec. Encourage your
customer to use standard syntax.
regards, tom lane
---(en
The problem I have with Bruce's scheme is that you could put your config
file where you want it and someone else puts one somewhere higher in the
search path and you have no idea what went wrong. It sounds to me like a
recipe for an SA's nightmare. Other people have claimed to speak from the SA
pe
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> The problem I have with Bruce's scheme is that you could put your config
> file where you want it and someone else puts one somewhere higher in the
> search path and you have no idea what went wrong. It sounds to me like a
> recipe for an SA's nightmar
On Wed, Feb 19, 2003 at 07:31:35AM -0500, Dave Cramer wrote:
> Bruce,
>
> Can you chime in with your support here?
>
> Dave
>
> I have a large customer who is converting from informix to postgres and
> they have made extensive use of
>
> update table set (col...) = ( val...)
>
> as a first pa
On 2003-02-18 20:02:29 +0100, Peter Eisentraut wrote:
> Christopher Kings-Lynne writes:
>
> > REPLACE INTO anyone? ;)
>
> The upcoming SQL 200x standard includes a MERGE command that appears to
> fulfill that purpose.
>
MySQL features a poor-mans aproach to this problem, their REPLACE command:
Patrick,
No, they support the syntax:
update table set (col1, col2, col3) = ( val1, val2, val3 )
I have a customer with a rather large application which uses this
syntax, because they were using informix. There is also a rather
interesting 4GL project called aubit which is on sourceforge. They w
I'm seeing this:
Welcome to psql 7.4devel, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit
nconway=> \d
nconwa
On Wednesday 19 February 2003 8:18 pm, Dave Cramer wrote:
> I have a customer with a rather large application which uses this
> syntax, because they were using informix. There is also a rather
> interesting 4GL project called aubit which is on sourceforge. They would
> also like to see this support
While I don't see the syntax of:
update table set (col...) = ( val...)
as valuable compared to separate col=val assignments, I do see a value
in allowing subqueries in such assignments:
update table set (col...) = ( select val ..)
Without it, you have to do separate subquery st
After a long battle with technology,[EMAIL PROTECTED] (Mike Aubury), an earthling, wrote:
> On Wednesday 19 February 2003 8:18 pm, Dave Cramer wrote:
>> I have a customer with a rather large application which uses this
>> syntax, because they were using informix. There is also a rather
>> interesti
While looking at this recent bug report (which still fails in CVS tip)
http://archives.postgresql.org/pgsql-bugs/2003-02/msg00094.php
I realized that the code paths that putatively exist for machines
with neither HAVE_TM_ZONE nor HAVE_INT_TIMEZONE have gone unused
since at least 6.5. Proof is that
On 19 Feb 2003, Dave Cramer wrote:
> Yes, the company in question is more than evaluating it; this request is
> a result of a project to port their application to postgres.
Ahh. I thought you were referring to IBM. That is, that IBM was evaluating
Postgres...
Gavin
---(
Hi,
I've been looking at the dependency API and I notice that there is a
function to delete ALL dependencies on an object and a function to add a
dependency, but there doesn't seem to be any way of deleting a dependency
between two _particular_ objects.
Is there any other way of doing this other
On 19 Feb 2003, Dave Cramer wrote:
> Justin,
>
> This is certainly the case here. I think IBM is deprecating informix,
> and many informix users are being forced to make a change, and they are
> seriously considering postgres as an alternative.
Do you have any evidence that they are evaluating i
Justin Clift <[EMAIL PROTECTED]> writes:
> As a thought, will it add significant maintenance penalties or be
> detrimental?
Well, yes it will if you look at the big picture. In the past we've
generally regretted it when we put in nonstandard features just to be
compatible with some other databas
Hi all,
(B
(BThere seems a bad behavior under autocommit off mode.
(B
(B 1) psql -c 'set autocommit to off;select 1;commit'
(Bcauses a WARNING: COMMIT: no transaction in progress
(Bwhereas
(B 2) psql -c 'begin;select 1;commit'
(Bcauses no error/warning.
(B
(BNote that the result is the
Agreed folks are going to have bigger problems from Informix than just
this, and in fact I used Informix for years and didn't know they allowed
this.
However, what solution do we have for UPDATE (coll...) = (select val...)
for folks? It is awkward to repeat a query multiple times in an UPDATE.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> While I don't see the syntax of:
> update table set (col...) = ( val...)
> as valuable compared to separate col=val assignments, I do see a value
> in allowing subqueries in such assignments:
> update table set (col...) = ( select val ..)
Hm.
Bruce Momjian wrote:
mlw wrote:
I raised the possibility of moving the pid file only last week. Tom
pointed out that it acts as a lock on the database to prevent two
postmasters' trying to manage the same database. As such it should NOT
be a configurable parameter.
This is a differe
On Wed, Feb 19, 2003 at 12:03:44AM +0100, Peter Eisentraut wrote:
> Ross J. Reedstrom writes:
>
> > Yes, BSD systems that install libedit directly in /usr/include (or into
> > readline), like Patrick's, don't need it, but mine do. Is there some
> > reason we _shouldn't_ support this configuration
Peter,
Referring to
http://src.doc.ic.ac.uk/packages/dbperl/refinfo/sql3/sql3bnf.sep93.txt
the following grammar exists
is the reference above valid?
as for tom's reply there are left paren, and right paren.
Dave
On Wed, 2003-02-19 at 10:37, Peter Eisentraut wrote:
> Dave Cramer writes:
>
>
On Wed, 2003-02-19 at 02:43, mlw wrote:
> PostgreSQL Extended Configuration Patch
...
> --- Run-time process ID ---
> postmaster -R /var/run/postmaster.pid
>
> This will direct PostgreSQL to write its process ID number
> to a file, /var/run/postgresql.conf
>
> --- postgresql.conf options ---
...
Christopher Kings-Lynne writes:
> *sigh* It's just like a standard to come up with a totally new syntax for a
> feature that no-one has except MySQL who use a different syntax :)
Actually that command was copied straight out of Oracle.
--
Peter Eisentraut [EMAIL PROTECTED]
-
The bytea type seems to be liable to character set conversions to the
effect that it falsifies the stored data.
Example: Create a cluster with non-C CTYPE, create a LATIN1 database,
create a table with a bytea column, and store something with non-ASCII
characters in it. Then change the client en
Oliver Elphick wrote:
On Wed, 2003-02-19 at 02:43, mlw wrote:
PostgreSQL Extended Configuration Patch
...
--- Run-time process ID ---
postmaster -R /var/run/postmaster.pid
This will direct PostgreSQL to write its process ID number
to a file, /var/run/postgresql.conf
--- postgresql.con
Dennis Björklund writes:
> What is the translation stats on
>
> http://webmail.postgresql.org/~petere/nls.php
>
> based on?
The 7.3 branch. Right now there's no point in working on 7.4 translations
anyway.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast
Dave Cramer writes:
> update table set (col...) = ( val...)
> It would appear that this is SQL3 compliant
>
> ::=
>
>
> ::=
>
> |
That's not what my copy says.
::=
[ { }... ]
::=
|
::=
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Ross J. Reedstrom wrote:
>> On Wed, Feb 19, 2003 at 12:03:44AM +0100, Peter Eisentraut wrote:
>>> I don't like adding code to support every configuration that someone
>>> dreamed up but no one actually needs.
>>
>> Hmm, isn't this exactly what configure i
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have a new idea. You know how we have search_path where you can
> specify multiple schema names. What if we allow the config_dirs/-C to
> specify multiple directories to search for config files. That way, we
> can use only one variable, and we can al
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 19 February 2003 15:02
> To: Dave Page
> Subject: RE: [webmaster] Figures from docs?
>
>
> >
> > The URL you give is just the index page. What's the exact URL of a
> > page that's missing a figure?
> >
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have a new idea. You know how we have search_path where you can
> > specify multiple schema names. What if we allow the config_dirs/-C to
> > specify multiple directories to search for config files. That way, we
> > can use only o
Bruce Momjian <[EMAIL PROTECTED]> writes:
> The bigger question is whether you can modify config_dirs while the
> postmaster is running. I would think not.
There would be no way to do that, because the only way to set it would
be from -C on the command line or a PGCONFIG environment variable.
But
Dave Cramer <[EMAIL PROTECTED]> writes:
> Referring to
> http://src.doc.ic.ac.uk/packages/dbperl/refinfo/sql3/sql3bnf.sep93.txt
> the following grammar exists
> is the reference above valid?
Sep 93? That would be an extremely early draft of what eventually became
SQL99. Looks like the parens got
Peter Eisentraut wrote:
In general, the only safe solution would be to escape *all* byte
values on output. Then the client can reconstruct the byte sequence based
on the character entities in the delivered string and does not have to
rely on the character codes staying the same during the conversi
Ok, if a patch were submitted to the parser to allow the syntax in
question would it be considered?
Dave
On Wed, 2003-02-19 at 12:29, Tom Lane wrote:
> Dave Cramer <[EMAIL PROTECTED]> writes:
> > Referring to
> > http://src.doc.ic.ac.uk/packages/dbperl/refinfo/sql3/sql3bnf.sep93.txt
> > the follow
Dave Cramer <[EMAIL PROTECTED]> writes:
> Ok, if a patch were submitted to the parser to allow the syntax in
> question would it be considered?
I would vote against it ... but that's only one vote.
regards, tom lane
---(end of broadcast)---
Tom Lane wrote:
(B>
(B> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
(B> > Tom Lane wrote:
(B> >> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
(B> >>> Is there a way to make our way around the pages ?
(B> >>
(B> >> If the header is corrupt, I don't think so.
(B>
(B> > What I asked is how to re
> While I don't see the syntax of:
>
> update table set (col...) = ( val...)
>
> as valuable compared to separate col=val assignments, I do see a value
> in allowing subqueries in such assignments:
>
> update table set (col...) = ( select val ..)
>
> Without it, you have to do separate subquery
Tom Lane wrote:
Dave Cramer <[EMAIL PROTECTED]> writes:
Ok, if a patch were submitted to the parser to allow the syntax in
question would it be considered?
I would vote against it ... but that's only one vote.
As a thought, will it add significant maintenance penalties or be
detrimental?
There
Justin,
This is certainly the case here. I think IBM is deprecating informix,
and many informix users are being forced to make a change, and they are
seriously considering postgres as an alternative.
It behooves us to look at aubit http://aubit4gl.sourceforge.net/ before
making this decision as w
> BTW, looking at the SQL99 standard, I see that you can do
>
> UPDATE table SET ROW = foo WHERE ...
>
> where foo is supposed to yield a row of the same rowtype as table
> --- I didn't dig through the spec in detail, but I imagine foo can
> be a sub-select. I don't care a whole lot for that, t
Christopher Kings-Lynne wrote:
>
> > BTW, looking at the SQL99 standard, I see that you can do
> >
> > UPDATE table SET ROW = foo WHERE ...
> >
> > where foo is supposed to yield a row of the same rowtype as table
> > --- I didn't dig through the spec in detail, but I imagine foo can
> > be a su
47 matches
Mail list logo
