ps. I've now put it up with some minor edits and formatting at
<http://wiki.postgresql.org/wiki/CTEReadme>. It is linked from the
Commitfest page.
> > Also, now that we are into August, would Asaba-san and whomever else
> > like to try out the git repository? To do so, I just need a login
Yoshiyuki). Also I added your SQL to the regression test,
> and now the patches is against CVS HEAD. For your convenience I also
> include patches against the previous version.
Thanks :)
Any progress on the READMEs for this?
Also, now that we are into August, would Asaba-san and whomever els
l, but the above SQL should work and
the error appears to stem from the parser's looking at the innermost
UNION ALL instead of the outermost.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfet
ath[1:2]
AND
array_upper(t1.path,1) = 2
AND
array_upper(t2.path,1) > 2
)
GROUP BY t1.id;
ERROR: unrecognized node type: 203
Please apply the attached patch to help out with tab
completion in psql.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 A
;")
at postgres.c:977
#15 0x0823e84c in PostgresMain (argc=4, argv=0xa0d0dac, username=0xa0d0d7c
"shackle") at postgres.c:3559
#16 0x0820957f in ServerLoop () at postmaster.c:3238
#17 0x0820a4e0 in PostmasterMain (argc=3, argv=0xa0ced50) at postmaster.c:1023
#18 0x081b69d6 in main (a
SELECT max(i) FROM t
UNION ALL
SELECT n+1 FROM x WHERE n < 20
)
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTED]
Remember to vote!
Consider donating to
On Fri, Jul 18, 2008 at 07:56:09AM -0700, David Fetter wrote:
> On Fri, Jul 18, 2008 at 10:41:20AM +0900, Tatsuo Ishii wrote:
> > > > Here is the lastest WITH RECURSIVE patches against CVS HEAD created by
> > > > Yoshiyuki Asaba and minor corrections by Tatsuo Ishii
8
5 | 10
(5 rows)
While this case is trivial, others are not. For example, if someone
wishes to do a k-deep summary on a parts explosion n levels deep, n>k,
one way to do this would be to JOIN the k-deep part of the path
enumeration to the parts greater than k deep.
What would need to b
it is now.
>
> For 3) I will generate regression tests as soon as possible.
>
> So the patches seem to be almost ready to commit IMO.
Wonderful!
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skyp
name at the moment.
>
> Also I suggest to concentrate on reviewing the WITH RECURSIVE
> implementation itself now, rather than discussing how to use git
> repository or how to write an interesting WITH RECURSIVE
> applications.
>
> Don't get me wrong. I believe git is a gre
ot valid acroding to the standard
> > > - sort query names acording to the dependency
> >
> > Is there something in the standard on how to do this? How to sort
> > the nodes other ways?
>
> No idea. What do you think if we allow only one query name at the
> moment.
etter/postgresql/.git;a=commit;h=da63f9a82b9e902b5542f788b2e6e6bc95221793
> Not yet fixed:
>
> - detect certain queries those are not valid acroding to the standard
> - sort query names acording to the dependency
Is there something in the standard on how to do this? How to sort the
nodes other ways?
Cheers,
Davi
On Wed, Jul 09, 2008 at 04:43:27PM -0400, Aidan Van Dyk wrote:
> * David Fetter <[EMAIL PROTECTED]> [080709 14:45]:
> > On Tue, Jul 08, 2008 at 09:28:34PM -0400, Alvaro Herrera wrote:
>
> > > In fact, I fail to see the point of you providing the repo if
> > >
On Tue, Jul 08, 2008 at 09:28:34PM -0400, Alvaro Herrera wrote:
> David Fetter wrote:
> > On Tue, Jul 08, 2008 at 06:01:05PM +0900, Tatsuo Ishii wrote:
> > > Here is the patches he made against CVS HEAD (as of today).
> >
> > The git repository should n
wing URL:
http://git.postgresql.org/git/~davidfetter/postgresql/.git
Is there some git repository I can pull from to make this a little
less manual?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfe
ttempting reset: Failed.
> > !> \q
> >
> > this one will kill the planner :(
> > removing the (totally stupid) distinct avoids the core dump.
>
> Thanks. I've fixed on local repository.
Asaba-san, do you have a patch against CVS HEAD or against the
previous
what do you think is going wrong here?
> i am looking forward to see this patch in core :).
So am I :)
> it is simply wonderful ...
>
> many thanks,
Thanks go to the kind people who actually wrote the thing. I've just
been using git to keep the bit-rot off it :)
Cheers,
D
Folks,
Please find patch enclosed, including some documentation.
Can we see about getting this in this commitfest?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PRO
their own serialization. A JSON or YAML one, for example, would be
much lighter weight on both ends.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTED]
Remember to vote!
Consi
y attached this time.
Can we see about getting this into the July commitfest? Dave has
presented a use case complete with logs where having this could have
prevented a failed backup and consequent data loss.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415
On Thu, Jun 12, 2008 at 12:33:57PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Mon, Jun 09, 2008 at 05:56:59PM -0700, Neil Conway wrote:
> >> I'm not necessarily opposed to this, but I wonder if we really
> >> need *more* synta
ke Pavel's would go a long way toward
getting developers actually to use them.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTED]
Remember to vote!
Consider donat
TO
> > somefile.
>
> Well, my primary reason for writing the patch was to have a standard
> SQL file using INSERT statements in order to load the some of a
> table's data into a database other than postgresql which does not
> support the COPY statement.
Have you t
On Sat, May 24, 2008 at 05:08:51AM -0700, David Fetter wrote:
> On Sun, May 18, 2008 at 08:51:29PM +0900, Tatsuo Ishii wrote:
> > WITH RECURSIVE patch V0.1
>
> Please find updated patch with bug fixes from Yoshiyuki Asaba and
> Michael Meskes. Any mistakes in it are mine. :)
On Sun, May 18, 2008 at 08:51:29PM +0900, Tatsuo Ishii wrote:
> WITH RECURSIVE patch V0.1
Please find updated patch with bug fixes from Yoshiyuki Asaba and
Michael Meskes. Any mistakes in it are mine. :)
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +
On Sat, May 24, 2008 at 05:01:11AM +0900, Yoshiyuki Asaba wrote:
> Hi,
>
> From: David Fetter <[EMAIL PROTECTED]>
> Subject: Re: [PATCHES] WITH RECURSIVE patch V0.1
> Date: Fri, 23 May 2008 11:26:30 -0700
>
> > Where is the new patch?
>
> I will create t
On Sat, May 24, 2008 at 03:21:01AM +0900, Yoshiyuki Asaba wrote:
> Hi,
>
> From: David Fetter <[EMAIL PROTECTED]>
> Subject: Re: [PATCHES] WITH RECURSIVE patch V0.1
> Date: Sun, 18 May 2008 11:47:37 -0700
>
> > I tried a bunch of different queries, and so far, onl
e just have it pay attention to the existing
max_stack_depth?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTED]
Remember to vote!
Consider donating to Postgres: http://w
l for a binary tree stored in a recursive table
> reference. The DBA might know that the data contains no loops but
> the database doesn't.
I seem to recall Oracle's implementation can do this traversal on
write operations, but maybe that's just their marketing.
Cheers,
Davi
ERE n < 100
)
SELECT * FROM t;
ERROR: cannot extract attribute from empty tuple slot
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTED]
Remember to vote!
Conside
ot coincidentally, moving all the checks into one spot, i.e. making
startup.c and command.c call and test the same things to connect to a
database, advances my Evil Plan™ to make more interesting things
happen when switching versions :)
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED
On Fri, May 16, 2008 at 01:22:55AM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > I believe there's a bug in this patch, namely that the warnings when
> > there's a server-client mismatch only appear at startup time.
>
> Please do not bl
On Thu, May 15, 2008 at 06:57:12PM -0400, Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > David Fetter wrote:
> >> I hate to bike-shed this even further, but I'd like to make those
> >> "incompatibility" messages just go away by mak
On Thu, May 15, 2008 at 06:55:31PM -0400, Andrew Dunstan wrote:
> David Fetter wrote:
>>
>> I hate to bike-shed this even further, but I'd like to make those
>> "incompatibility" messages just go away by making 8.4's psql (and
>> all those going fo
sql (and all
those going forward) support every living version of Postgres at the
time of their release, so 8.4's psql would be able to talk seamlessly
to Postgres 7.4 :)
Cheers,
David (well, not really bike-shedding, but trying to propose a feature
that reduces the amount of UI clutter)
--
David Fet
On Tue, May 13, 2008 at 01:53:33PM -0700, David Fetter wrote:
> On Tue, May 13, 2008 at 11:36:57AM -0400, Tom Lane wrote:
> > David Fetter <[EMAIL PROTECTED]> writes:
> > >>> Surely this is merely proof of concept and not a complete patch.
> > >>
>
On Tue, May 13, 2008 at 11:36:57AM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> >>> Surely this is merely proof of concept and not a complete patch.
> >>
> >> Next patch attached :)
>
> Uh, my point was that the agreement
On Tue, May 13, 2008 at 08:14:51AM -0700, David Fetter wrote:
> On Tue, May 13, 2008 at 10:47:40AM -0400, Alvaro Herrera wrote:
> > Tom Lane escribió:
> > > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > > David Fetter escribi?:
> > > >> Thanks
On Tue, May 13, 2008 at 10:47:40AM -0400, Alvaro Herrera wrote:
> Tom Lane escribió:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > David Fetter escribi?:
> > >> Thanks for the heads-up :)
> > >>
> > >> Second patch attached, t
bloat the
> output quite a lot, I think I'd vote for putting it in \dT+.
Here's one where it's only in \dT+
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMA
On Sun, May 04, 2008 at 06:40:51PM -0400, Andrew Dunstan wrote:
>
>
> David Fetter wrote:
>> Folks,
>>
>> In psql, \dT doesn't show the elements for enums. Please find
>> patch vs. CVS TIP attached which fixes this per the following TODO
>> item:
>&g
On Thu, May 01, 2008 at 10:53:00PM -0400, Andrew Dunstan wrote:
> David Fetter wrote:
>> Folks,
>>
>> In psql, \dT doesn't show the elements for enums. Please find
>> patch vs. CVS TIP attached which fixes this per the following TODO
>> item:
>>
>
On Wed, Apr 30, 2008 at 03:43:54PM +0100, Simon Riggs wrote:
> On Wed, 2008-04-30 at 07:31 -0700, David Fetter wrote:
> > On Wed, Apr 30, 2008 at 12:49:44PM +0100, Simon Riggs wrote:
> > > On Wed, 2008-04-30 at 11:29 +0100, Heikki Linnakangas wrote:
> > > > This c
we'd end up having before/after
> commands and retry options etc.
Would those be good things to have as a whole package?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter
Folks,
In psql, \dT doesn't show the elements for enums. Please find patch
vs. CVS TIP attached which fixes this per the following TODO item:
http://archives.postgresql.org/pgsql-hackers/2008-01/msg00826.php
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Ph
On Sun, Apr 06, 2008 at 11:29:50PM +0100, Gregory Stark wrote:
> I wonder if there's much of a use case for any statements aside from
> CREATE statements.
Yes. Some modules could have COPY or equivalent in them, as they
could easily contain data.
Cheers,
David.
--
David Fet
re objection there is that there is no easy
> way to see only the user-defined functions. Given your point quoted
> first above, I'm unconvinced that should be the default behavior.
When we have a bad default--and I'd argue that for anyone not
developing PostgreSQL itself, showing sy
>
> Yeah, I have to had two reason for this patch. First is my personal,
> because I don't like these names since 1999. And second is that
> Solaris architects do not like these names. Especially createdb and
> createuser. It could clash with some system utility.
+1 for re
ey'd fail the bigint regression test if not. That's not the point
> here.
If we don't have buildfarm coverage for machines where INT64_IS_BUSTED,
how do we know we support those architectures at all?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone:
e on CVS TIP, as the project does
not add new features to stable releases.
How do you want to be named on this?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTED]
t;> the situation where people have turned on INTEGER_DATETIMES?
> >>>
> >>> Cheers,
> >>> David.
> >>> --
> >>> David Fetter http://fetter.org/
> >>> Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
> >>>
On Mon, Jan 28, 2008 at 07:55:53PM +, Dean Rasheed wrote:
>
> > Dean,
> >
> > Maybe I missed something obvious here, but how does this patch handle
> > the situation where people have turned on INTEGER_DATETIMES?
> >
> > Cheers,
> > David.
> >
ean.
Dean,
Maybe I missed something obvious here, but how does this patch handle
the situation where people have turned on INTEGER_DATETIMES?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidf
> the COPY operation will not be so straightforward.
Folks,
Does my latest patch attached address this well enough?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROT
are talking about partitioning. It is supposed to be narrow-minded.
>
> Sure, but look at all the confusion we have had just on this list about
> it. We had better state why triggers should be used in place of rules
> _for_ _partitioning_ or that confusion will continue.
Please find enc
On Thu, Nov 29, 2007 at 12:55:53AM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Wed, Nov 28, 2007 at 09:58:26PM -0500, Jonah H. Harris wrote:
> >> On Nov 28, 2007 3:53 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> >>> Entirely remov
f one use case where using RULEs rather than
TRIGGERs is a good idea?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTED]
Remember to vote!
Consider donating to Postgres:
On Wed, Nov 28, 2007 at 10:06:01PM -0300, Alvaro Herrera wrote:
> David Fetter wrote:
>
> > Greg Sabino Mullane managed to contrive an example where RULEs
> > might conceivably be the least-bad way to do this, that being a
> > machine where no PLs may be installed.
>
&
On Wed, Nov 28, 2007 at 05:17:38PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Wed, Nov 28, 2007 at 03:53:04PM -0500, Tom Lane wrote:
> >> Entirely removing the example of how to do it with rules doesn't
> >> seem like a good
On Wed, Nov 28, 2007 at 03:53:04PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > Best practices for partitioning so far have shown that TRIGGERs
> > are better than RULEs for most cases. Please find attached a
> > patch which reflects this.
On Wed, Nov 28, 2007 at 12:41:20PM -0800, David Fetter wrote:
> On Wed, Nov 28, 2007 at 12:39:04PM -0800, Joshua D. Drake wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Wed, 28 Nov 2007 12:26:15 -0800
> > David Fetter <[EMAIL
On Wed, Nov 28, 2007 at 12:39:04PM -0800, Joshua D. Drake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wed, 28 Nov 2007 12:26:15 -0800
> David Fetter <[EMAIL PROTECTED]> wrote:
>
> > Folks,
> >
> > Best practices for partitioning so f
Folks,
Best practices for partitioning so far have shown that TRIGGERs are
better than RULEs for most cases. Please find attached a patch which
reflects this.
Thanks to Robert Treat for help putting this together :)
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Please don't do that; it would
> > confuse users about the versioning scheme.
>
> Would 8x be the right thing then?
>
> So PostgreSQL8xDialect or PostgreSQL80Dialect or ...
I'd say 80 so it's easy to separate off 81, 82, 83, etc. :)
Cheers,
David.
--
David Fette
On Sat, Nov 03, 2007 at 12:44:07PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > I think a prefix of ':' would be good, as it's already a standard,
> > kinda. Anybody who names a database object :foo deserves whatever
> > happens t
mple:
>
> where
> c.catid = this.p_category or
> t.typeid = this.p_type;
>
>
>
> Any thoughts?
I think a prefix of ':' would be good, as it's already a standard,
kinda. Anybody who names a database object :foo de
On Sun, Jul 01, 2007 at 09:03:45PM -0700, Neil Conway wrote:
> On Sun, 2007-01-07 at 12:55 -0700, David Fetter wrote:
> > Here's a new patch + file. This one allows ALTER [SEQUENCE | VIEW] to
> > work only on the respective database objects, but permits the old
> > AL
ire away.
>
> (I'm still not sure you found all the relevant places in the
> documentation, however.)
Here's a new patch + file. This one allows ALTER [SEQUENCE | VIEW] to
work only on the respective database objects, but permits the old
ALTER TABLE syntax.
Cheers,
David.
On Wed, May 16, 2007 at 03:53:22PM +0100, Gregory Stark wrote:
> "David Fetter" <[EMAIL PROTECTED]> writes:
>
> > On Wed, May 16, 2007 at 09:12:23AM +0100, Heikki Linnakangas wrote:
> >> Jim C. Nasby wrote:
> >> >BTW, is there some trick to gett
he lines starting with '?' that diff
produces.
Lacking sophistication, I've been known to do:
cvs diff [list of files here] |grep -v '^?' > the_file.diff
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter
On Mon, May 14, 2007 at 03:31:40PM +1200, Mark Kirkwood wrote:
> David Fetter wrote:
> >cvs diff works just great until you want to add or remove a file
> >without write permissions to the CVS repository, i.e. when you've
> >checked out as anonymous.
> >
>
>
On Sun, May 13, 2007 at 10:06:40PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > Per Neil Conway, here's some doc patches re: the autovacuum
> > daemon's behavior. Should this be back-patched to 8.2x?
>
> This fact is already docum
On Sun, May 13, 2007 at 09:51:53PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Sun, May 13, 2007 at 07:04:44PM -0400, Andrew Dunstan wrote:
> >> Tom Lane wrote:
> >>> Strange, it works fine for everyone else.
> >>
> >
Folks,
Thanks to Andrew Dunstan for pointing me toward cvsutils. As not
everybody knows about them, here's a small patch which lets people
know at least in theory where they are.
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM:
On Sun, May 13, 2007 at 07:04:44PM -0400, Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
> >David Fetter <[EMAIL PROTECTED]> writes:
> >
> >>I haven't included the customary diffs. This points me to some of
> >>the many deficiencies of CVS, nam
Folks,
Per Neil Conway, here's some doc patches re: the autovacuum daemon's
behavior. Should this be back-patched to 8.2x?
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
Skype: david
nsider using Git, which includes a CVS interface,
starting after 8.3 gets out the door?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donati
or
> \cnowait. I'm not sure if going for cryptic short commands is better
> or worse here.
+1 for \c1, \c2, etc.
What's the reasoning behind \c&? Does it "send things into the
background" the way & does in the shell?
Cheers,
David.
--
David Fetter <[EMAIL PROT
nclined to say we should prevent direct operations on array
> types, and they should live or die by their parent types.
>
> Thoughts?
+1 on binding the array types tightly to the parent types.
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415
On Mon, Apr 09, 2007 at 09:08:31PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Mon, Apr 09, 2007 at 06:43:08PM -0400, Tom Lane wrote:
> >> So this does not really add any new functionality, it's just variant
> >> syntax for someth
the full recursive-WITH feature before taking the
> compatibility hit.
Is there some way to poll people for uses of WITH and SET in places
they shouldn't be?
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
[12,13],null,null,null));
> ERROR: ROW() column has type integer[] instead of type anyarray
>
> but I don't feel comfortable about this at all. Maybe
> CheckAttributeType should be made to recurse into composite columns.
That'd be great :)
Cheers,
D
--
David Fe
s? It's not
> going to be anything but a toy unless you can get the per-entry
> overhead down to something sane. Perhaps the MinimalTuple
> representation would work.
Sounds neat, too :)
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 4
l GRANT/REVOKE, which
we don't have yet.
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/a
On Tue, Apr 03, 2007 at 02:30:07AM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Mon, Apr 02, 2007 at 10:01:44PM -0400, Alvaro Herrera wrote:
> >> So, hum, what happened to the idea of creating the array types
> >> only on demand?
>
ing, and partly because the closest
thing I've heard to an objection is pretty nebulous. :)
It's a lot simpler to have them always, and it fits in with the larger
picture of making arrays fully composable with other operations like
DOMAIN, ENUM and TYPE.
Cheers,
D
--
David Fetter <
On Fri, Mar 30, 2007 at 05:08:42PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > After several rounds of patches, it appears that it might be easier to
> > create a new typtype entry, which I'll tentatively call 'a' because it
> >
actually stepping up and doing it, not in the feature itself.
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.post
ld you please re-send?
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate
-
ce. What is the use case for
> > > getting all of prematch, fullmatch, matches, and postmatch in one
> > > call?
> >
> > It was requested by David Fetter:
> > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00056.php
> >
> > It was not horribly diffi
On Fri, Feb 16, 2007 at 01:03:32PM -0500, Andrew Dunstan wrote:
> David Fetter wrote:
> >>
> >>The question is, what is the use case? If there is one in Perl, can
> >>this proposed function API support it?
> >>
> >
> >Perl makes t
On Fri, Feb 16, 2007 at 05:54:47PM +0100, Peter Eisentraut wrote:
> Am Freitag, 16. Februar 2007 17:11 schrieb David Fetter:
> > > As for the regexp_matches() function, it seems to me that it
> > > returns too much information at once. What is the use case for
> >
() function, it seems to me that it returns
> too much information at once. What is the use case for getting all
> of prematch, fullmatch, matches, and postmatch in one call?
If not in one call, how would you get it? Perl, for example, makes
these available to any regex match in the form o
On Thu, Feb 15, 2007 at 07:35:46PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > I've obviously misunderstood the scope of the TODO because it appears
> > that an INSERT into pg_type at creation time for compound types that
> > looks some
ality to a function in form of a
> parameter.
That's what things like Perl's split do :)
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
Skype: davidfetter
Remember to vote!
different? */
-1, /* no typmod */
0 /* dims not specified */
);
> that would foreclose responding to Peter's concern that SETOF is the
> wrong thing. If you look at the Perl and Tcl APIs for regexes, they
> return just the strings, not the numeri
egate
>SELECT join(',', col) FROM tbl
> currently can be written as
>SELECT array_to_string(ARRAY(SELECT col FROM tbl), ',')
The array_accum() aggregate in the docs works OK for this purpose.
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]>
least in spirit.
> > > How about
> > >
> > > ... terminated by signal 10: Bus error
> >
> > I like that.
>
> OK, but you guys added back that colon you didn't like. :-)
Placement is crucial. Compare
terminated by signal 10: Bus error <-- proposed ver
On Tue, Dec 26, 2006 at 01:10:03PM +0100, Joachim Wieland wrote:
> On December 26, 5:19 am David Fetter <[EMAIL PROTECTED]> wrote:
> > It doesn't need the semicolon. PL/PgSQL's BEGIN is different from
> > SQL's. :)
>
> Exactly. Note that my patch _
3,7 +1243,7 @@
> to catch the error, for example:
>
>
> -BEGIN;
> +BEGIN
> SELECT * INTO STRICT myrec FROM emp WHERE empname = myname;
> EXCEPTION
> WHEN NO_DATA_FOUND THEN
>
> ---(end of broadcast)---
1 - 100 of 234 matches
Mail list logo
