Tom Lane wrote:
Jorgen Austvik - Sun Norway [EMAIL PROTECTED] writes:
I believe the results paths in line 139 and 144 are missing the
@abs_builddir@ qualifier.
I'd put it the other way around: likely we should get rid of the
one use of @[EMAIL PROTECTED]
He, he.
Generally I prefer explicit
On Nov 30, 2007 9:09 PM, Gregory Stark [EMAIL PROTECTED] wrote:
I'm sorry to suggest anything at this point, but... would it be less invasive
if instead of requiring the immediate cast you created a special case in the
array code to allow a placeholder object for empty array of unknown type.
Hi,
I updated the brazilian FAQ; it's in [1]. I'm attaching a small patch
that adds a forgotten question and change to lt;.
[1] http://timbira.com/tmp/FAQ_brazilian.html
--
Euler Taveira de Oliveira
http://www.timbira.com/
*** ./doc/src/FAQ/FAQ.html.orig 2007-11-30 22:39:02.0
On Fri, Nov 30, 2007 at 12:34:05PM +0530, NikhilS wrote:
Hi,
Another reason to go along with triggers is that COPY honors
triggers, but does not honor rules. While trying to do bulk inserts
into a parent of partitioned tables where rules are being employed,
the COPY operation will not be so
Brendan Jurd [EMAIL PROTECTED] writes:
The patch is very invasive (at least compared to any of my previous
patches), but so far I haven't managed to find any broken behaviour.
I'm sorry to suggest anything at this point, but... would it be less invasive
if instead of requiring the immediate
As discussed on -hackers, this patch allows the construction of an
empty array if an explicit cast to an array type is given (as in,
ARRAY[]::int[]).
postgres=# select array[]::int[];
array
---
{}
postgres=# select array[];
ERROR: no target type for empty array
HINT: Empty arrays must be
Alvaro Herrera [EMAIL PROTECTED] writes:
Jorgen Austvik - Sun Norway wrote:
Tom Lane wrote:
I'd put it the other way around: likely we should get rid of the
one use of @[EMAIL PROTECTED]
Generally I prefer explicit over implicit (having the full paths make
troubleshooting easier), but in
On Thu, 2007-11-29 at 09:52 -0800, Joshua D. Drake wrote:
In any of the above cases a trigger is going to work better than a
rule with the exceptions of what TGL pointed out and in simpler
partitioning environments where the number of partitions are very low.
Agreed to this and in general to
Jorgen Austvik - Sun Norway wrote:
Tom Lane wrote:
Jorgen Austvik - Sun Norway [EMAIL PROTECTED] writes:
I believe the results paths in line 139 and 144 are missing the
@abs_builddir@ qualifier.
I'd put it the other way around: likely we should get rid of the
one use of @[EMAIL PROTECTED]
I wrote:
OK, I have a fairly ugly manual workaround, that I don't yet
understand, but seems to work for me.
In your session, run the following code before you do anything else:
CREATE OR REPLACE FUNCTION test(text) RETURNS bool LANGUAGE plperl as $$
return shift =~ /\xa9/i ? 'true' :
10 matches
Mail list logo