> > SHOW
> >
> >
> > I think 7.4 could and really should implement SHOW command similar to
> > MySQL. Listing tables/foreign keys/views and so isn't just psql problem,
>
> Actually, in 7.4 I'd tell them to:
>
> select * from information_schema.tables;
>
> This is a far more portable metho
On Wed, 2003-01-22 at 04:55, Antti Haapala wrote:
> SHOW
>
>
> I think 7.4 could and really should implement SHOW command similar to
> MySQL. Listing tables/foreign keys/views and so isn't just psql problem,
Actually, in 7.4 I'd tell them to:
select * from information_schema.tables;
This
Ups... i sent an early draft of my post by accident, sorry...
--
Antti Haapala
+358 50 369 3535
ICQ: #177673735
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTE
SHOW
I think 7.4 could and really should implement SHOW command similar to
MySQL. Listing tables/foreign keys/views and so isn't just psql problem,
but common to many interface implementations and maintenance tools. I
think it's wrong to rely on pg_* system tables on these.
If you think o
;[EMAIL PROTECTED]>; "Al Sutton"
<[EMAIL PROTECTED]>; "Stephen L." <[EMAIL PROTECTED]>; "PostgresSQL Hackers
Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 10, 2002 8:04 PM
Subject: Re: [mail] Re: [HACKERS] 7.4 Wishlist
> Hello,
>
Yes, the issue was that give our TODO list, compressed transfer wasn't
very high, and it was unknown how valuable it would be. However, if it
were contributed, we could easily test its value with little work on our
part and include the code if it were a win.
-
On Tue, 2002-12-10 at 13:38, Bruce Momjian wrote:
> I haven't heard anything about them contributing it. Doesn't mean it
> will not happen, just that I haven't heard it.
>
This was in non-mailing list emails that I was told this by Joshua Drake
at Command Prompt. Of course, that doesn't have t
Greg Copeland wrote:
> On Tue, 2002-12-10 at 11:25, Al Sutton wrote:
> > Would it be possible to make compression an optional thing, with the default
> > being off?
> >
>
> I'm not sure. You'd have to ask Command Prompt (Mammoth) or wait to see
> what appears. What I originally had envisioned w
. Hope you guys don't
mind.
Greg
> - Original Message -
> From: "Greg Copeland" <[EMAIL PROTECTED]>
> To: "Stephen L." <[EMAIL PROTECTED]>
> Cc: "PostgresSQL Hackers Mailing List" <[EMAIL PROTECTED]>
> Sent: Tuesday, D
se packets uncompressed.
Al.
- Original Message -
From: "Greg Copeland" <[EMAIL PROTECTED]>
To: "Stephen L." <[EMAIL PROTECTED]>
Cc: "PostgresSQL Hackers Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 10, 2002 4:56 PM
Subject: [mail]
On Tue, 2002-12-10 at 09:36, Stephen L. wrote:
> 6. Compression between client/server interface like in MySQL
>
Mammoth is supposed to be donating their compression efforts back to
this project, or so I've been told. I'm not exactly sure of their
time-line as I've slept since my last conversatio
Hi, if I may add to the wishlist for 7.4 in order of importance. Some items
may have been mentioned or disputed already but I think they are quite
important:
1. Avoid needing REINDEX after large insert/deletes or make REINDEX not use
exclusive lock on table.
2. Automate VACUUM in background and ma
Kevin Brown wrote:
> How useful would it be? Beats me. Like I said, you could perform
> some "what if" games with a database this way that you currently
> can't, but I don't know how useful that would be. On thinking about
> it a bit, it seems option 1 would be the most useful and perhaps the
>
Tom Lane wrote:
> "Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> > Mysql is planning on making this work:
> > SELECT id, @a:=COUNT(*), SUM(sum_col)/@a FROM table_name GROUP BY id.
>
> We're supposed to spend our time emulating nonstandard features that
> don't even exist yet? I think I have
Bruce Momjian wrote:
> Kevin Brown wrote:
> > I'd also like to see (if this is even possible) a transaction
> > isolation mode that would make it possible for multiple concurrent
> > updates to the same row to happen without blocking each other (I
> > imagine one way to make this possible would be
Kevin Brown wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> > Hi guys,
> >
> > Just out of interest, if someone was going to pay you to hack on Postgres
> > for 6 months, what would you like to code for 7.4?
>
> Well, on top of the oft-requested replication support and savepoint
> s
Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> Just out of interest, if someone was going to pay you to hack on Postgres
> for 6 months, what would you like to code for 7.4?
Well, on top of the oft-requested replication support and savepoint
support, I'd like to see UPDATE, er,
- Original Message -
From: "Kevin Brown" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 03, 2002 8:49 PM
Subject: [mail] Re: [HACKERS] 7.4 Wishlist
> Al Sutton wrote:
> > Point to Point and Broadcast replication
> >
Hi:
We at the Department of Information Technology of the Mindanao State
University-Iligan Institute of Technology (MSU-IIT) in Iligan City,
Philippines had been using PostgreSQL since 1998 in teaching courses in
Databases, SQL, and as a support tool in teaching Software Engineering and
Web App
Marc G. Fournier wrote:
Actually, there are lines, Justin just occasionally appears to 'blur' them
until I get a chance to refresh them ... eh Justin?:)
[innocent whistle]
+ Justin
---(end of broadcast)---
TIP 1: subscribe and unsubscribe comma
Marc G. Fournier wrote:
On Tue, 3 Dec 2002, Justin Clift wrote:
Excellent. Are there any other people involved in PostgreSQL and
universities or educational institutions? If so we could put something
together about experiences for the advocacy Web site.
Is this the kind of thing that the Tech
Joe Conway writes:
> That is one thing I'd like to take a look at. I think the problem is that
> certain byte-sequence/multibyte-encoding combinations are illegal, so it's not
> as simple an issue as it might first appear.
The bytea type really shouldn't come even close to having to care about
th
> The one good reason for making it possible to use raw partitions is to
> make it possible to use the PostgreSQL engine as a filesystem! :-)
Hmm.. Something just doesn't seem right about that thought ;)
CREATE DATABASE filesystem;
\c filesystem
CREATE EXPORT /mnt AS NFS;
\q
mount_nfs -o port
Hi ...
I just wanted to admit that an important collegue in Vienna already uses
PostgreSQL instead of Oracle which makes me really proud :).
We have done a training course this year and they use PostgreSQL instead
of free Oracle
I am happy that Austrian students are tortured with the things I ha
On 3 Dec 2002 at 15:08, Vince Vielhaber wrote:
> Where have you been? The lines of distinction between all of the
> lists have gotten so blurred it hardly makes a difference.
So consider this a wake up call.
--
Dan Langille : http://www.langille.org/
---(end of broadca
Al Sutton wrote:
> Point to Point and Broadcast replication
>
> With point to point you specify multiple endpoints, with broadcast you can
> specify a subnet address and the updates are broadcast over that subnet.
>
> The difference being that point to poin
On Tue, 3 Dec 2002, Vince Vielhaber wrote:
> On Tue, 3 Dec 2002, Marc G. Fournier wrote:
>
> > On Tue, 3 Dec 2002, Justin Clift wrote:
> >
> > > > Excellent. Are there any other people involved in PostgreSQL and
> > > > universities or educational institutions? If so we could put something
> > > >
On Tue, 3 Dec 2002, Marc G. Fournier wrote:
> On Tue, 3 Dec 2002, Justin Clift wrote:
>
> > > Excellent. Are there any other people involved in PostgreSQL and
> > > universities or educational institutions? If so we could put something
> > > together about experiences for the advocacy Web site.
>
On Tue, 3 Dec 2002, Justin Clift wrote:
> > Excellent. Are there any other people involved in PostgreSQL and
> > universities or educational institutions? If so we could put something
> > together about experiences for the advocacy Web site.
>
> Is this the kind of thing that the Techdocs Guides a
TODO updated. Thanks for the clarification.
---
Hannu Krosing wrote:
> On Tue, 2002-12-03 at 16:00, Bruce Momjian wrote:
> > Is WITH a TODO item?
>
> It is disguised as
>
> Exotic Features
> ===
>
> * Add sq
On Tue, 2002-12-03 at 16:00, Bruce Momjian wrote:
> Is WITH a TODO item?
It is disguised as
Exotic Features
===
* Add sql3 recursive unions
Which was added at my request in dark times, possibly when PostgreSQL
was called postgres95 ;)
This should be changed to two items
* Add SQ
Is WITH a TODO item?
---
Hannu Krosing wrote:
> On Tue, 2002-12-03 at 09:20, Dennis Bj?rklund wrote:
> > On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
> >
> > > Now convert this query so that it only evaluates the date_part
On 3 Dec 2002, Hannu Krosing wrote:
> the standard way of doing it would be SQL99's WITH :
Great! I havn't looked too much at sql99 yet so I've missed this. It's
exactly what I want. Now I know what I will use in the future (when it's
all implemented).
--
/Dennis
---
I'm certainly interested! I am working here on Geographical Information
Systems with PostgreSQL/PostGIS with the Minnesota MapServer, with a lot
of regular database work thrown in. PostgreSQL has great potential for
teaching databases and SQL, and when the native Windows port is ready,
it will
On Tue, 2002-12-03 at 09:20, Dennis Björklund wrote:
> On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
>
> > Now convert this query so that it only evaluates the date_part thing
> > ONCE:
> >
> > select t.id, date_part('days',now()-t.stamp) from table_name t where
> > date_part('days',now()-t.stamp
On Mon, Dec 02, 2002 at 12:48:38PM -0800, Christopher Kings-Lynne wrote:
> But if there is, then the sum/count(*) is nonsensical anyway.
You must to use it in SERIALIZABLE transaction isolation.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
-
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
> Now convert this query so that it only evaluates the date_part thing
> ONCE:
>
> select t.id, date_part('days',now()-t.stamp) from table_name t where
> date_part('days',now()-t.stamp) > 20;
Something like this could work:
select *
from (select t
"Magnus Naeslund(f)" <[EMAIL PROTECTED]> writes:
> Mysql is planning on making this work:
> SELECT id, @a:=COUNT(*), SUM(sum_col)/@a FROM table_name GROUP BY id.
We're supposed to spend our time emulating nonstandard features that
don't even exist yet? I think I have better things to do ...
On Tue, 3 Dec 2002, Bruce Momjian wrote:
> Magnus Naeslund(f) wrote:
> > Good!
> > Now convert this query so that it only evaluates the date_part thing
> > ONCE:
> >
> > select t.id, date_part('days',now()-t.stamp) from table_name t where
> > date_part('days',now()-t.stamp) > 20;
> >
> > I hope y
Stephan Szabo <[EMAIL PROTECTED]> wrote:
> On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
>
>> Now convert this query so that it only evaluates the date_part thing
>> ONCE:
>
> That's not a good idea as long as t.stamp varies from row to row. ;)
> Perhaps once per row, maybe... :)
>
I give up
On Tue, 3 Dec 2002, Magnus Naeslund(f) wrote:
> Now convert this query so that it only evaluates the date_part thing
> ONCE:
That's not a good idea as long as t.stamp varies from row to row. ;)
Perhaps once per row, maybe... :)
> select t.id, date_part('days',now()-t.stamp) from table_name t wh
Magnus Naeslund(f) wrote:
> Good!
> Now convert this query so that it only evaluates the date_part thing
> ONCE:
>
> select t.id, date_part('days',now()-t.stamp) from table_name t where
> date_part('days',now()-t.stamp) > 20;
>
> I hope you all are kidding me in not seeing the real issue i'm tryi
> Good!
> Now convert this query so that it only evaluates the date_part thing
> ONCE:
>
> select t.id, date_part('days',now()-t.stamp) from table_name t where
> date_part('days',now()-t.stamp) > 20;
Yes, it's a bit of a bugger that one.
> I hope you all are kidding me in not seeing the real issu
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Magnus Naeslund(f) wrote:
>>> select id, sum(sum_col)||'/'||count(*) from table_name
>>> group by id;
>>>
>>> or
>>>
>>> select table_name.id, sum(sum_col)||'/'||t2.count from table_name,
>>> (select id, count(*) as count from table_name group by id) as
Magnus Naeslund(f) wrote:
> > select id, sum(sum_col)||'/'||count(*) from table_name
> > group by id;
> >
> > or
> >
> > select table_name.id, sum(sum_col)||'/'||t2.count from table_name,
> > (select id, count(*) as count from table_name group by id) as t2 where
> > table_name.id=t2.id group by t
Gavin Sherry wrote:
On Mon, 2 Dec 2002, Christopher Kings-Lynne wrote:
I've given a talk in the 2002 honours lecture series at UWA about Postgres
and some of the things it can do. All of those guys were interested.
Especially since the deptartment does a lot of work in genetic algoriithms.
On Mon, 2 Dec 2002, Christopher Kings-Lynne wrote:
> I've given a talk in the 2002 honours lecture series at UWA about Postgres
> and some of the things it can do. All of those guys were interested.
> Especially since the deptartment does a lot of work in genetic algoriithms.
Excellent. Can you
> I might get together with some of the lecturers I've worked with in
> Sydney to give such a document some weight. I must say, the problem is not
> a technical one though. I've given talks to 3rd and 4th year students
> about PostgreSQL -- technical, conceptual, political talks... you name
> it. O
Gavin Sherry wrote:
I want to see:
i) proper resource management a-la Oracle. This would allow a DBA to
limited the amount of time any given user spends in the parser, planner or
executor. It would be limited with a more sophisticated user system,
including things like CREATE USER PROFILE ...
A
On Mon, 2 Dec 2002, Christopher Kings-Lynne wrote:
> > viii) General advocacy, particularly in pushing mainstream IT media
> > coverage, conferences and university usage -- both for teaching SQL and
> > for teach database engineering concepts for senior undergrads.
>
> Definitely. How about a re
> i) proper resource management a-la Oracle. This would allow a DBA to
> limited the amount of time any given user spends in the parser, planner or
> executor. It would be limited with a more sophisticated user system,
> including things like CREATE USER PROFILE ...
Hehehe - yeah this would be nea
I want to see:
i) proper resource management a-la Oracle. This would allow a DBA to
limited the amount of time any given user spends in the parser, planner or
executor. It would be limited with a more sophisticated user system,
including things like CREATE USER PROFILE ...
ii) Auditing. Who acces
Hannu Krosing <[EMAIL PROTECTED]> wrote:
> Magnus Naeslund(f) kirjutas T, 03.12.2002 kell 03:18:
>> It looks like it (7.2.x):
>>
>> # time psql genline -c "select id from " > /dev/null
>> real0m0.694s
>> user0m0.147s
>> sys 0m0.025s
>> # time psql genline -c "select id,id||'/'||(sel
Magnus Naeslund(f) kirjutas T, 03.12.2002 kell 03:18:
> It looks like it (7.2.x):
>
> # time psql genline -c "select id from " > /dev/null
> real0m0.694s
> user0m0.147s
> sys 0m0.025s
> # time psql genline -c "select id,id||'/'||(select count(*) from )
> as x from " > /dev/
On Mon, 2 Dec 2002, Magnus Naeslund(f) wrote:
> Stephan Szabo <[EMAIL PROTECTED]> wrote:
> >
> > If you use a scalar subquery, yes, but I think a subselect in from
> > would help, maybe something like (if you want the total count)
> >
> > select table_name.id, sum(sum_col)||'/'||t2.count from tabl
Stephan Szabo <[EMAIL PROTECTED]> wrote:
>
> If you use a scalar subquery, yes, but I think a subselect in from
> would help, maybe something like (if you want the total count)
>
> select table_name.id, sum(sum_col)||'/'||t2.count from table_name,
> (select count(*) as count from table_name) as t2
Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> Are you sure that postgres evaluates that subselect more than once?
> It looks to me like it returns a constant result for every row and
> hence it will be evaluated once per statement, not once per row. I'm
> no expert tho. Can someone answer t
On Mon, 2 Dec 2002, Magnus Naeslund(f) wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> >> Mysql is planning on making this work:
> >>
> >> SELECT id, @a:=COUNT(*), SUM(sum_col)/@a FROM table_name GROUP BY
> >> id.
> >>
> >> Do we have anything like it (After a discussion with Tom i
> Yeah, but there is a point about running count(*) one time too many.
> Say if i would like to get a prettyprinting query like this:
>
> SELECT id, @a:=COUNT(*), sum_col::text||'/'@a::text FROM table_name;
>
> That would be DAMN expensive doing with a subselect:
>
> SELECT id, sum_col||'/'||(selec
Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
>> Mysql is planning on making this work:
>>
>> SELECT id, @a:=COUNT(*), SUM(sum_col)/@a FROM table_name GROUP BY
>> id.
>>
>> Do we have anything like it (After a discussion with Tom i figure
>> no). User variables is nice, especially in these ki
> Mysql is planning on making this work:
>
> SELECT id, @a:=COUNT(*), SUM(sum_col)/@a FROM table_name GROUP BY id.
>
> Do we have anything like it (After a discussion with Tom i figure no).
> User variables is nice, especially in these kind of queries.
Well of course they have to make that work
Mysql is planning on making this work:
SELECT id, @a:=COUNT(*), SUM(sum_col)/@a FROM table_name GROUP BY id.
Do we have anything like it (After a discussion with Tom i figure no).
User variables is nice, especially in these kind of queries.
Nice would be to be able to use them as in C (almost e
Joe Conway wrote:
> David Wheeler wrote:
> > My understanding is that the nul character is legal in a byte sequence,
> > but if it's not properly escaped, it'll be parsed as the end of the
> > statement. Unfortunately, I think that it's a very tough problem to solve.
>
> No question wrt '\0' byt
How about giving OLAP (Dimension / Measure) functionality to PG.
Catch all the cricket action. Download
Yahoo! Score tracker
>> my wish:
>>
>> * error codes. It's very interesting that nobody other wants it...
>
>I do :-)
>
Me too. It is a must in my opinion..
Regards,
Nic.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister comman
Native Windows port
Plz don't forget poor victims of Microsoft
!!!
> -Original Message-
> From: Karel Zak [mailto:[EMAIL PROTECTED]]
> Sent: 02 December 2002 11:26
> To: Christopher Kings-Lynne
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] 7.4 Wishlist
>
>
> On Fri, Nov 29, 2002 at 10:51:26AM -0800, Christopher
>
On Fri, Nov 29, 2002 at 10:51:26AM -0800, Christopher Kings-Lynne wrote:
> Hi guys,
>
> Just out of interest, if someone was going to pay you to hack on Postgres
> for 6 months, what would you like to code for 7.4?
This is interesting discussion..
my wish:
* error codes. It's very intere
Christopher Kings-Lynne writes:
> Just out of interest, if someone was going to pay you to hack on Postgres
> for 6 months, what would you like to code for 7.4?
Well judging by the hoards on Slashdot, it would appear that
replication is the hot enhancement...
Slashdot | PostgreSQL 7.3 Released
David Wheeler wrote:
My understanding is that the nul character is legal in a byte sequence,
but if it's not properly escaped, it'll be parsed as the end of the
statement. Unfortunately, I think that it's a very tough problem to solve.
No question wrt '\0' bytes -- they would have to be escaped
On Sun, 1 Dec 2002, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > On 30 Nov 2002, Neil Conway wrote:
> >> Have we decided how this would even work? Last I heard, Tom still had
> >> some major reservations about the practicality of implementing these --
> >> for example, would you
Stephan Szabo <[EMAIL PROTECTED]> writes:
> On 30 Nov 2002, Neil Conway wrote:
>> Have we decided how this would even work? Last I heard, Tom still had
>> some major reservations about the practicality of implementing these --
>> for example, would you re-evaluate all constraints that SELECT from a
"Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
> pg_dump, our upgrade process is painful enough having to do a dump,
> reload. I think we should be able to guarantee (or at least let
> much closer to it) that the process works in all cases.
I would already be happy if pg_dump backed up my dat
On 30 Nov 2002, Neil Conway wrote:
> On Sat, 2002-11-30 at 12:47, Stephan Szabo wrote:
> > check constraints with subselects.
>
> Have we decided how this would even work? Last I heard, Tom still had
> some major reservations about the practicality of implementing these --
> for example, would yo
Joe Conway <[EMAIL PROTECTED]> writes:
>- possibly enhanced connectby functionality (may not be worth it if
> RECURSIVE JOIN functionality makes it into 7.4)
Several of my Red Hat cohorts are pretty interested in making the
RECURSIVE query stuff work for 7.4. (The fact that they're ex-DB
On Saturday, November 30, 2002, at 07:24 PM, Joe Conway wrote:
That is one thing I'd like to take a look at. I think the problem is
that certain byte-sequence/multibyte-encoding combinations are
illegal, so it's not as simple an issue as it might first appear.
My understanding is that the nul
David Wheeler wrote:
On Saturday, November 30, 2002, at 04:14 PM, Joe Conway wrote:
Not quite sure what you mean by delimiter -- are you referring to double
escaping vs single escaping?
Oh crap, yes, that's exactly what I meant.
s/delimited/escaped/g;
That is one thing I'd like to take a l
On Sat, 2002-11-30 at 12:47, Stephan Szabo wrote:
> check constraints with subselects.
Have we decided how this would even work? Last I heard, Tom still had
some major reservations about the practicality of implementing these --
for example, would you re-evaluate all constraints that SELECT from a
> > My ones are:
> >
> > * Compliant ADD COLUMN
> > * Integrated full text indexes
> > * pg_dump dependency ordering
> >
> > What would you guys do? Even if it isn't feasible right now...
Actually - I think I might add MODIFY COLUMN to that list. Just look at the
list of poor buggers in the inte
On Saturday, November 30, 2002, at 04:14 PM, Joe Conway wrote:
Not quite sure what you mean by delimiter -- are you referring to
double
escaping vs single escaping?
Oh crap, yes, that's exactly what I meant.
s/delimited/escaped/g;
Sorry. :-)
David
--
David Wheeler
David Wheeler wrote:
On Saturday, November 30, 2002, at 01:44 PM, Joe Conway wrote:
* continue to improve usability of bytea datatype
- easier explicit casting between bytea and text
This wouldn't happen to include the idea of somehow eliminating the
difference between how text strings are
Cross-db queries.
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.po
On Saturday, November 30, 2002, at 01:44 PM, Joe Conway wrote:
* continue to improve usability of bytea datatype
- easier explicit casting between bytea and text
This wouldn't happen to include the idea of somehow eliminating the
difference between how text strings are delimited and how byt
Christopher Kings-Lynne wrote:
Hi guys,
Just out of interest, if someone was going to pay you to hack on Postgres
for 6 months, what would you like to code for 7.4?
My ones are:
* Compliant ADD COLUMN
* Integrated full text indexes
* pg_dump dependency ordering
What would you guys do? Even if
Can you see this tying in with my recent hack of contrib/ltree to work
with a wider range of node names?
On Sat, 30 Nov 2002, Oleg Bartunov wrote:
> Me and Teodor hope to work on contrib/ltree to add support for sort of
> xml. Any ideas are welcome !
---(end of broadcast
On Sat, 2002-11-30 at 15:06, bpalmer wrote:
> > * Compliant ADD COLUMN
>
> I've missed the thread (if there was one), how is it non-compliant?
ALTER TABLE .. ADD COLUMN colname integer DEFAULT 42 NOT NULL
CHECK(colname <= 42) REFERENCES tab2 ON DELETE CASCADE;
Can't do the above in a single sta
> * Compliant ADD COLUMN
I've missed the thread (if there was one), how is it non-compliant?
Thanks,
- Brandon
c: 917-697-8665h: 201-798-4983
b. palmer, [EMAIL PROTECTED]
Me and Teodor hope to work on contrib/ltree to add support for sort of
xml. Any ideas are welcome !
Regards,
Oleg
On Fri, 29 Nov 2002, Christopher Kings-Lynne wrote:
> Wow Hannu - your list puts mine to shame!
>
> > "Application server support"
> > ---
Hi All,
here is my wishlist /very short/ :
* Oracle syntax support in OUTER JOIN
Thanks, Gabor
> Hans-Jürgen Schönig wrote:
> > What I'd like to have in future versions of PostgreSQL:
> >
> > - PL/Sh should be in contrib. i know that the core team has decided
> > not to put it in the core
On Fri, 29 Nov 2002, Christopher Kings-Lynne wrote:
> Just out of interest, if someone was going to pay you to hack on Postgres
> for 6 months, what would you like to code for 7.4?
> What would you guys do? Even if it isn't feasible right now...
Hmm, mine would probably be fixing foreign keys
Hannu Krosing wrote:
> On Sat, 2002-11-30 at 16:13, Bruce Momjian wrote:
> > Hans-J?rgen Sch?nig wrote:
> > > What I'd like to have in future versions of PostgreSQL:
> > >
> > > - PL/Sh should be in contrib. i know that the core team has decided
> > > not to put it in the core but contrib woul
On Sat, 2002-11-30 at 16:13, Bruce Momjian wrote:
> Hans-Jürgen Schönig wrote:
> > What I'd like to have in future versions of PostgreSQL:
> >
> > - PL/Sh should be in contrib. i know that the core team has decided
> > not to put it in the core but contrib would be fine (I keep forgetting
> >
Hans-Jürgen Schönig wrote:
> What I'd like to have in future versions of PostgreSQL:
>
> - PL/Sh should be in contrib. i know that the core team has decided
> not to put it in the core but contrib would be fine (I keep forgetting
> the URL of Peters website :( ...)
I like PL/Sh too, but too
On Sat, 2002-11-30 at 05:55, Alvaro Herrera wrote:
> On Fri, Nov 29, 2002 at 10:51:26AM -0800, Christopher Kings-Lynne wrote:
>
> > Just out of interest, if someone was going to pay you to hack on Postgres
> > for 6 months, what would you like to code for 7.4?
>
> Well, nobody is paying me, but I
On Friday 29 November 2002 06:51 pm, Christopher Kings-Lynne wrote:
> Hi guys,
>
> Just out of interest, if someone was going to pay you to hack on Postgres
> for 6 months, what would you like to code for 7.4?
>
> My ones are:
>
> * Compliant ADD COLUMN
> * Integrated full text indexes
> * pg_dump
one (and working) by the end of June.
Obviously, any kind of hint and suggestion by you guruz is welcome! :)
Bye, alice
- Original Message -
From: "Christopher Kings-Lynne" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 29, 2002 7:51 PM
Subject: [H
> And that's all ;)
>
> Hannu Krosing
- and what will you do after January? ;-)
Just kidding. I hope you have a big fat bank account if you want to finish
all that!
--
Kaare Rasmussen--Linux, spil,--Tlf:3816 2582
Kaki Datatshirts, me
-
I've explained the reasons before. Apart from that it's always useful to
open PostgreSQL up to a larger audience.
- Original Message -
From: "Daniele Orlandi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 29, 2002 11:06 PM
Subject: [ma
Oops, there is something I have forgotten:
- "nicing" backends: this would be nice for administration tasks
- CREATE DATABASE ... WITH MAXSIZE (many providers would like to see
that; quotas are painful in this case - especially when porting the
database to a different or a second server)
What I'd like to have in future versions of PostgreSQL:
- replication, replication, ... (you have seen that before). i guess
most people would like to see that.
- a dblink like system for connecting to remote database systems
(not just PostgreSQL???)
something like CREATE REMOTE VI
1 - 100 of 113 matches
Mail list logo
