On Mon, Nov 14, 2005 at 17:10:58 -0700,
Aly Dharshi <[EMAIL PROTECTED]> wrote:
> Would the PG Dev group be working on update-able views for 8.2 ? I know
> that there is a work-around using rules, the SAMS book does claim that 8.0
> has readonly views. I don't think that this has changed in 8.1
Aly Dharshi wrote:
> Would the PG Dev group be working on update-able views for 8.2 ? I know that
> there is a work-around using rules, the SAMS book does claim that 8.0 has
> readonly views. I don't think that this has changed in 8.1 no ?
>
We don't know what will be in 8.2 until a volunteer d
Hi all,
karen hill wrote:
> What do you see for 8.2 and beyond? What type of
> features are you devs planning for 9.0? It would be
> good if you could put up a place on your site so we
> mortals can drool over up-coming postgresql features.
I'm wishing
- more audit facilities
- pluggable/load
Would the PG Dev group be working on update-able views for 8.2 ? I know that
there is a work-around using rules, the SAMS book does claim that 8.0 has
readonly views. I don't think that this has changed in 8.1 no ?
Cheers,
Aly.
Bruce Momjian wrote:
[EMAIL PROTECTED] wrote:
Gavin Sherry:
[EMAIL PROTECTED] wrote:
> > Gavin Sherry:
> > Grouping sets
> > Recursive queries
>
> The recursive queries is a long-awaited feature. Does the fact that the
> feature is listed for Gavin Sherry mean that Gavin is actually working
> with the feature at the moment? Does anybody kno
[EMAIL PROTECTED] (Gavin Sherry) writes:
> Hi,
>
> On Tue, 14 Nov 2005 [EMAIL PROTECTED] wrote:
>
>> > Gavin Sherry:
>> > Grouping sets
>> > Recursive queries
>>
>> The recursive queries is a long-awaited feature. Does the fact that
>> the feature is listed for Gavin Sherry mean th
Hi,
On Tue, 14 Nov 2005 [EMAIL PROTECTED] wrote:
> > Gavin Sherry:
> > Grouping sets
> > Recursive queries
>
> The recursive queries is a long-awaited feature. Does the fact that the
> feature is listed for Gavin Sherry mean that Gavin is actually working
> with the feature at the
> Gavin Sherry:
> Grouping sets
> Recursive queries
The recursive queries is a long-awaited feature. Does the fact that the
feature is listed for Gavin Sherry mean that Gavin is actually working
with the feature at the moment? Does anybody know the current state of
this feature or
Tom Lane wrote:
Patrick Bakker <[EMAIL PROTECTED]> writes:
It would be useful if you could toggle SQL statement logging without
restarting PostgreSQL and additionally if you could turn on selective SQL
logging. Additionally, it would be great if you could log SQL statements to
a separate fil
/me has started working on hierarchical query support that I'd like to get into 8.2.On 10/17/05, Tom Lane <[EMAIL PROTECTED]
> wrote:Dave Cramer <[EMAIL PROTECTED]
> writes:> On 17-Oct-05, at 1:43 PM, Martijn van Oosterhout wrote:>> ISTM them that the RETURNING patch as given solves your problem>>
Dave Cramer <[EMAIL PROTECTED]> writes:
> On 17-Oct-05, at 1:43 PM, Martijn van Oosterhout wrote:
>> ISTM them that the RETURNING patch as given solves your problem
>> nicely.
> Well, the driver still needs to know ahead of time which columns are
> going to be autogenerated.
Possibly you coul
Patrick Bakker <[EMAIL PROTECTED]> writes:
> It would be useful if you could toggle SQL statement logging without
> restarting PostgreSQL and additionally if you could turn on selective SQL
> logging. Additionally, it would be great if you could log SQL statements to
> a separate file from the main
: Friday, October 14, 2005 9:57 AM
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] PostgreSQL roadmap for 8.2 and beyond.
Autovacuum is getting put into the 8.1 release which
is awesome. A lot of us are wondering now that
PostgreSQL has all the features that many of us need,
what are the features
On 17-Oct-05, at 1:43 PM, Martijn van Oosterhout wrote:
On Mon, Oct 17, 2005 at 01:32:22PM -0400, Dave Cramer wrote:
The JDBC problem at hand is there is a method which allows one to
retrieve the
autogenerated keys from an insert. I can understand Tom's argument
here. It should
be possible fo
On Mon, Oct 17, 2005 at 01:32:22PM -0400, Dave Cramer wrote:
> The JDBC problem at hand is there is a method which allows one to
> retrieve the
> autogenerated keys from an insert. I can understand Tom's argument
> here. It should
> be possible for the driver to build a query from the meta data
Dave Cramer wrote:
On the other hand given that all of the serial increments are stored
in the session is it possible to
get the results of the last insert on the session ? If we can avoid
the extra query so much
the better, but either way is better than what we have ?
Would that no
On 17-Oct-05, at 12:43 PM, Tom Lane wrote:
Martijn van Oosterhout writes:
On Mon, Oct 17, 2005 at 09:12:35AM -0400, Dave Cramer wrote:
AFAIKS, the protocol needs to be tweaked to return at a minimum the
currval for the first serial in the row, but more correctly all of
the modified currval
Martijn van Oosterhout writes:
> On Mon, Oct 17, 2005 at 09:12:35AM -0400, Dave Cramer wrote:
>> AFAIKS, the protocol needs to be tweaked to return at a minimum the
>> currval for the first serial in the row, but more correctly all of
>> the modified currval's for an insert
> In what sense? It s
On Mon, Oct 17, 2005 at 09:12:35AM -0400, Dave Cramer wrote:
> I fail to see how this solves the problem of getting auto generated
> keys.
>
> AFAIKS, the protocol needs to be tweaked to return at a minimum the
> currval for the first serial in the row, but more correctly all of
> the modifi
lt;[EMAIL PROTECTED]>
To: "Bruce Momjian"
Cc: "Neil Conway" <[EMAIL PROTECTED]>; "PostgreSQL-development"
Sent: Monday, October 17, 2005 6:12 AM
Subject: Re: [HACKERS] PostgreSQL roadmap for 8.2 and beyond.
I fail to see how this solves the problem of ge
I fail to see how this solves the problem of getting auto generated
keys.
AFAIKS, the protocol needs to be tweaked to return at a minimum the
currval for the first serial in the row, but more correctly all of
the modified currval's for an insert
if we had that then we could correctly imp
Neil Conway wrote:
> On Sun, 2005-16-10 at 01:20 -0700, Kevin McArthur wrote:
> > Don't forget insert/update returning.
>
> Omar Kilani has a patch for this:
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00568.php
>
> I would like to see it get into 8.2
Yes, this is in the 8.2 pat
On Sun, 2005-16-10 at 01:20 -0700, Kevin McArthur wrote:
> Don't forget insert/update returning.
Omar Kilani has a patch for this:
http://archives.postgresql.org/pgsql-patches/2005-07/msg00568.php
I would like to see it get into 8.2
-Neil
---(end of broadcast)
On Sun, Oct 16, 2005 at 01:20:45AM -0700, Kevin McArthur wrote:
> Don't forget insert/update returning. With the deprecation of OID's this
> functionality is becoming more and more important when using custom types
> and column defaults.
I use currval/nextval and have never actually needed such a
PROTECTED]>
To: "karen hill" <[EMAIL PROTECTED]>
Cc:
Sent: Saturday, October 15, 2005 6:16 PM
Subject: Re: [HACKERS] PostgreSQL roadmap for 8.2 and beyond.
On Fri, 2005-10-14 at 09:57 -0700, karen hill wrote:
Autovacuum is getting put into the 8.1 release which
is awesome. A l
On Fri, 2005-10-14 at 09:57 -0700, karen hill wrote:
> Autovacuum is getting put into the 8.1 release which
> is awesome. A lot of us are wondering now that
> PostgreSQL has all the features that many of us need,
> what are the features being planned for future
> releases?
You know, as PostgreSQL
Autovacuum is getting put into the 8.1 release which
is awesome. A lot of us are wondering now that
PostgreSQL has all the features that many of us need,
what are the features being planned for future
releases?
What do you see for 8.2 and beyond? What type of
features are you devs planning for 9.
27 matches
Mail list logo
