[HACKERS] request for sql3 compliance for the update command
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 set clause ::= update target equals operator row value designator update target ::= object column | left paren object column list right paren or can someone think of another way? -- Dave Cramer [EMAIL PROTECTED] Cramer Consulting ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] location of the configuration files
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 place different config files in different directories. That's an interesting idea. Were you thinking, perhaps, that you could put, say, a postgresql.conf file in multiple directories and have the settings in the latest one override the settings in earlier ones? That would mean you could set up a single postgresql.conf that has settings common to all of your instances (settings related to the system such as shared buffers, and default settings that would apply to any instance if not overridden), and a postgresql.conf file for each instance that defines the instance-specific configuration information. I'm not sure that's quite what you had in mind, though. :-) -- Kevin Brown [EMAIL PROTECTED] ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] request for sql3 compliance for the update command
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 It would appear that this is SQL3 compliant set clause ::= update target equals operator row value designator update target ::= object column | left paren object column list right paren or can someone think of another way? -- Dave Cramer [EMAIL PROTECTED] Cramer Consulting ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] psql problem in 7.2.3
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? -- Felipe Schnack Analista de Sistemas [EMAIL PROTECTED] Cel.: (51)91287530 Linux Counter #281893 Centro Universitário Ritter dos Reis http://www.ritterdosreis.br [EMAIL PROTECTED] Fone/Fax.: (51)32303341 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] request for sql3 compliance for the update command
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 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 set clause ::= update target equals operator row value designator update target ::= object column | left paren object column list right paren or can someone think of another way? I don't understand the original problem. What does informix give you? A text file full of update table set ()=() which you then try to feed into postgres? In that case, why not pass said text file through a sed or perl script first? Cheers, Patrick ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Hard problem with concurrency
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: http://www.mysql.com/doc/en/REPLACE.html REPLACE works exactly like INSERT, except that if an old record in the table has the same value as a new record on a UNIQUE index or PRIMARY KEY, the old record is deleted before the new record is inserted. I'd love to see this kind of functionality in PG, I've got a database that caches data which only gets conditional INSERT/UPDATEs, so that would save a lot of wasted SQL commands. Vincent van Leeuwen Media Design ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] request for sql3 compliance for the update 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 would also like to see this supported for the same reasons. Dave On Wed, 2003-02-19 at 15:02, Patrick Welche wrote: 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 set clause ::= update target equals operator row value designator update target ::= object column | left paren object column list right paren or can someone think of another way? I don't understand the original problem. What does informix give you? A text file full of update table set ()=() which you then try to feed into postgres? In that case, why not pass said text file through a sed or perl script first? Cheers, Patrick -- Dave Cramer [EMAIL PROTECTED] Cramer Consulting ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] psql regression in CVS HEAD
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 nconway= create table a (b int); CREATE TABLE nconway= \d nconway= \dS nconway= \d a nconway= (i.e. all the slash commands seem to be returning no output: the server log show the queries are being sent to the backend, but no output is produced by psql). That's with current CVS, on Linux with libreadline4.3 Cheers, Neil -- Neil Conway [EMAIL PROTECTED] || PGP Key ID: DB3C29FC ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] request for sql3 compliance for the update command
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 supported for the same reasons. Hey - I was going to say that... For the curious: Quick URL - http://aubit4gl.sourceforge.net/ Its a 'clone' of the Informix 4GL tool, a nice 'clean' language specifically designed for writing database applications, with both curses GTK, support for multiple database types and a bunch of other things... We're about to release version 0.30 - and I was going to wait until then ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] request for sql3 compliance for the update command
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 statements, and if they are complex, that is a waste. I assume that was the motivation for the feature. --- Dave Cramer wrote: 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 would also like to see this supported for the same reasons. Dave On Wed, 2003-02-19 at 15:02, Patrick Welche wrote: 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 set clause ::= update target equals operator row value designator update target ::= object column | left paren object column list right paren or can someone think of another way? I don't understand the original problem. What does informix give you? A text file full of update table set ()=() which you then try to feed into postgres? In that case, why not pass said text file through a sed or perl script first? Cheers, Patrick -- Dave Cramer [EMAIL PROTECTED] Cramer Consulting ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] request for sql3 compliance for the update command
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 interesting 4GL project called aubit which is on sourceforge. They would also like to see this supported for the same reasons. Hey - I was going to say that... For the curious: Quick URL - http://aubit4gl.sourceforge.net/ Its a 'clone' of the Informix 4GL tool, a nice 'clean' language specifically designed for writing database applications, with both curses GTK, support for multiple database types and a bunch of other things... We're about to release version 0.30 - and I was going to wait until then I tried it out a while back; couldn't get it to compile, probably due to there being a bit too much 'bleeding' to the 'bleeding edge.' It looks as though it could be pretty interesting, if PG support matures (which can certainly be a two way street!). How's the cross-platform support? Aubit would be an easier sell, to be sure, if it is readily deployable on Those Other Platforms, too... -- (concatenate 'string cbbrowne @acm.org) http://www.ntlug.org/~cbbrowne/multiplexor.html MSDOS didn't get as bad as it is overnight -- it took over ten years of careful development. -- [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Simplifying timezone support
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 abstime2tm() doesn't even compile in that code path (it has a reference to an undefined variable now). Since we evidently have no supported platforms that have neither method of learning the timezone, I propose that we stop contorting the code with the illusion that we can handle this case reasonably. We can easily set it up so that we just default to GMT when neither config symbol is defined. The reason I want to do this is to remove the dependency on system-supplied values of CTimeZone and CTZName. CTZName can go away altogether (ditto CDayLight), and CTimeZone will only be used when the user explicitly sets a timezone as a numeric offset from GMT (ie, the HasCTZSet paths). This will save cycles during every transaction start, where we currently expend time setting these values (see GetCurrentAbsoluteTimeUsec). And it will fix the above-mentioned bug, which exists because CTimeZone is set at transaction start and not updated by a later SET TIMEZONE command. The bug could be fixed, sort of, by calling GetCurrentAbsoluteTimeUsec again after executing SET TIMEZONE. But there is a variant scenario where the same bug exists: if there has been a daylight-savings transition since the current transaction started, we'll still get the wrong answers. So trying to make CTimeZone track the current timezone correctly seems doomed to failure anyhow. Any objections? regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] request for sql3 compliance for the update command
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 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[HACKERS] deleting dependencies
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 than manually deleting the row from the pg_depend table? I'm messing about with changing column type and I need to drop the dependency on the old type and add the dependency on the new type Chris ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] request for sql3 compliance for the update command
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 it? Gavin ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] request for sql3 compliance for the update command
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 database. (Tatsuo already pointed out the foo = NULL fiasco.) And we get ragged on regularly for the non-SQL- standard features we've inherited from Berkeley Postgres (eg, the implicit-FROM frammish that was under discussion yesterday). I don't think we're really doing the users any favor either. If they want to move to some other database after Postgres, are they likely to get that other database to insert a not-very-useful nonstandard syntax? Sooner or later they're going to have to bite this bullet, and it may as well be sooner. (I can hardly believe that this is the worst compatibility issue an ex-Informix user would face, anyhow.) This is an Informix-ism. It should stay that way. regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] A bad behavior under autocommit off mode
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 same even when you issue (Bthe first set/begin command separately using the client (Bsoftwares other than psql. (B (BThe problem here is that the transaction is cancelled (Bin case of 1) though no error is reported. (BShouldn't we avoid the warning and the cancellation ? (BOr should an error be reported instead of the warning ? (B (Bregards, (BHiroshi Inoue (Bhttp://www.geocities.jp/inocchichichi/psqlodbc/ (B (B---(end of broadcast)--- (BTIP 2: you can get off all lists at once with the unregister command (B(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] translation stats
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)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] request for sql3 compliance for the update command
Dave Cramer writes:
update table set (col...) = ( val...)
It would appear that this is SQL3 compliant
set clause ::=
update target equals operator row value designator
update target ::=
object column
| left paren object column list right paren
That's not what my copy says.
set clause list ::=
set clause [ { comma set clause }... ]
set clause ::=
update target equals operator update source
| mutated set clause equals operator update source
update target ::=
object column
| ROW
| object column
left bracket or trigraph simple value specification right
bracket or trigraph
object column ::= column name
mutated set clause ::=
mutated target period method name
mutated target ::=
object column
| mutated set clause
update source ::=
value expression
| contextually typed value specification
(And I'm pretty sure I have the right version of the standard.)
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] psql and readline
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 is for? Configure is for such tests --- you are right, and we already test two places. I have to side with Ross also. Configure makes many tests that are designed for situations much less common than his. I don't see the reason for refusing to accommodate this one. (Not that I've looked at the details of the patch, mind you. But in principle it seems reasonable.) regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] location of the configuration files
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 allow people to place different config files in different directories. Hm, a search path for config files? I could support that if it satisfies the folks who object to specifying config directories rather than file names. One thing that would have to be thought about is whether to re-search the path on each config file reload --- if you first find pg_hba.conf in, say, the third directory on the path, should you pay attention if one materializes in the second directory later? Or do you keep going back to the same well? I can see arguments either way. regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [webmaster] Figures from docs?
-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?
Regards, Dave.
Hi,
For example this one,
http://www.postgresql.org/docs/view.php?version=7.3idoc=1file=parser-s
tage.html#AEN51838
Here I can find \ref{parsetree} in stead of what I think it has to
be a picture, the picture of a parse tree generated by the parser
stage in the example from the documentation.
It hapens the same in the pdf version of the documentation.
Hmm, I see what you mean. That seems to be a problem in the SGML-HTML
conversion as that's also what I see in the HTML files from the tarball.
Perhaps someone on the hackers list who knows the doc generation process
can help?
Regards, Dave.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] location of the configuration files
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 one variable, and we can allow people to place different config files in different directories. Hm, a search path for config files? I could support that if it satisfies the folks who object to specifying config directories rather than file names. One thing that would have to be thought about is whether to re-search the path on each config file reload --- if you first find pg_hba.conf in, say, the third directory on the path, should you pay attention if one materializes in the second directory later? Or do you keep going back to the same well? I can see arguments either way. Oh, I hadn't thought of that. I would vote for researching the path, but I am not sure why. The bigger question is whether you can modify config_dirs while the postmaster is running. I would think not. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] location of the configuration files
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 I can't see a real good reason why you'd need to. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] request for sql3 compliance for the update command
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 lost again by the time of the final spec. Given that there's no visible functionality gain from allowing parens here, I'm not surprised that the spec authors decided it wasn't such a hot idea after all... too bad Informix didn't get the word :-( regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Bytea misconceptions
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 conversion. Seems like this brings us back to using hex for bytea, ala BLOB in SQL99. What would be the implications of changing byteain and byteaout to use X'FF' instead of '\377\377\377'? I guess backward compatibility is a big problem. Maybe make it configurable: all octal escaped or all hex. Is it better to create a completely new datatype? Joe ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] request for sql3 compliance for the update command
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 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 lost again by the time of the final spec. Given that there's no visible functionality gain from allowing parens here, I'm not surprised that the spec authors decided it wasn't such a hot idea after all... too bad Informix didn't get the word :-( regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org -- Dave Cramer [EMAIL PROTECTED] Cramer Consulting ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] request for sql3 compliance for the update command
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)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Detecting corrupted pages earlier
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 read all other sane pages. (B (B Oh, I see. You can do "SELECT ... LIMIT n" to get the rows before the (B broken page, but there's no way to get the ones after it. My proposal (B won't make this worse, but it won't make it any better either. Do you (B have an idea how to get the rows after the broken page? (B (BHow about adding a new option to skip corrupted pages ? (B (Bregards, (BHiroshi Inoue (Bhttp://www.geocities.jp/inocchichichi/psqlodbc/ (B (B---(end of broadcast)--- (BTIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] request for sql3 compliance for the update command
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 statements, and if they are complex, that is a waste. I assume that was the motivation for the feature. The number of times I've needed this feature... :) Chris ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] request for sql3 compliance for the update command
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 seem to be quite a lot of Informix people moving to PostgreSQL these days, moreso than Oracle shops. Might have been brought on by IBM's purchase of Informix. Wondering if this one change be a significant improvement in regards to making it easier to migrate, or just a minor thing? Regards and best wishes, Justin Clift regards, tom lane -- My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there. - Indira Gandhi ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] request for sql3 compliance for the update command
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 well. I believe the aubit project has the potential to move postgres forward considerably as well. Dave On Wed, 2003-02-19 at 21:08, Justin Clift wrote: 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 seem to be quite a lot of Informix people moving to PostgreSQL these days, moreso than Oracle shops. Might have been brought on by IBM's purchase of Informix. Wondering if this one change be a significant improvement in regards to making it easier to migrate, or just a minor thing? Regards and best wishes, Justin Clift regards, tom lane -- Dave Cramer [EMAIL PROTECTED] Cramer Consulting ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] request for sql3 compliance for the update command
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, though, since it would be a real pain in the neck if you're not updating all the columns. You'd have to go UPDATE table SET ROW = (SELECT table.a, table.b, foo.x, ... FROM foo) How is the Informix syntax any better? Chris ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] request for sql3 compliance for the update command
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 sub-select. I don't care a whole lot for that, though, since it would be a real pain in the neck if you're not updating all the columns. You'd have to go UPDATE table SET ROW = (SELECT table.a, table.b, foo.x, ... FROM foo) How is the Informix syntax any better? With Informix, you specify the columns you want updated in parens, rather than saying ROW. Does the spec allow a list of columns after ROW? That would be nice, like Informix. I doubt many folks update all the columns. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
