Where exactly would you propose to stick it in the syntax?
Good question, I don't know.
Can you do
it without introducing more fully-reserved words than we have already?
No idea.
Is there any spec or other-product precedent for it? (Offhand I can't
even find CREATE TABLE AS in SQL99...)
Weeell.
On Mon, 2004-04-19 at 02:16, Tom Lane wrote:
> (Offhand I can't even find CREATE TABLE AS in SQL99...)
This is semi-OT, but CREATE TABLE AS is (new) in SQL2003. At few glance,
the spec's notion of the command is about the same as ours, except for a
few minor syntactic differences (e.g. the [ WITH
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Is there any reason why the 'ON COMMIT' behaviour feature is not
> available if you use CREATE TABLE AS ...?
Where exactly would you propose to stick it in the syntax? Can you do
it without introducing more fully-reserved words than we have a
Hello
I've did pg_dumpall of a number of databases on 7.4.2 install of
PostgreSQL then imported that into another 7.4.2 install. This is on
Debian Sid, every 5 hours, there's a script
/usr/lib/postgresql/bin/do.maintenance which runs on the database,
VACUUMing it and such. The next time that scrip
Is there any reason why the 'ON COMMIT' behaviour feature is not
available if you use CREATE TABLE AS ...?
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I wrote:
> Dennis Bjorklund <[EMAIL PROTECTED]> writes:
>> This testcase works in 7.3 but not in 7.4:
>> create table t1 (a int);
>> create table t2 (b int);
>> select * from t1, (select b as a from t2 group by a) as foo;
> Another tweak we could make is to cause findTargetlistEntry() to look
> o
Kris Jurka <[EMAIL PROTECTED]> writes:
> When executing a prepared select statement, the returned RowDescription
> protocol message does not have any information for the table oid or column
> position. Running the equivalent select without prepare provides this
> information, so I don't see why th
Andrew Dunstan wrote:
Christopher Kings-Lynne said:
But you would have to assign the copyright to them
If someone is going to make money from my code, I prefer it to be me,
or at least that everyone has a chance to do so rather than just one
company.
Well, then for the same reas
Shachar Shemesh wrote:
Tom Lane wrote:
These tools are a not insignificant part of our Plan for World
Domination ;-) so it would be good if somebody stepped up to the
plate and volunteered to take care of 'em. Anybody?
Which brings me to another question
I have a bunch of perl scripts, as
When executing a prepared select statement, the returned RowDescription
protocol message does not have any information for the table oid or column
position. Running the equivalent select without prepare provides this
information, so I don't see why the act of preparing and executing the
statement
Tom Lane wrote:
These tools are a not insignificant part of our Plan for World
Domination ;-) so it would be good if somebody stepped up to the
plate and volunteered to take care of 'em. Anybody?
Which brings me to another question
I have a bunch of perl scripts, as well as one user-defined t
Christopher Kings-Lynne said:
>> But you would have to assign the copyright to them
>>
>> If someone is going to make money from my code, I prefer it to be me,
>> or at least that everyone has a chance to do so rather than just one
>> company.
>
> Well, then for the same reason we should writ
12 matches
Mail list logo
