Joe Conway <[EMAIL PROTECTED]> writes:
> You seem to be saying that because the output of certain functions that operate
> on empty arrays is NULL, it somehow implies that the array is being treated as
> NULL -- that's just plain incorrect.
Not incorrect, but a sign something weird is going on.
Greg Stark wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
Same here; this would be:
array_upper(a || b) == array_upper(a) + CARDINALITY(b)
and would work just fine. Note that if array-a is NULL, then the spec defines a
|| b as NULL. See section 6.35:
Why are you talking about when a is NULL? The
Ana Cerejo <[EMAIL PROTECTED]> writes:
> I am trying a pre-load a user table during InitPostgres. I tried to mimic
> the relevant actions in ReverifyDatabase to carry this out. I manage to
> load the first block of the table. However, if a table is more than 1
> block, I end up getting warnin
Joe Conway <[EMAIL PROTECTED]> writes:
> Same here; this would be:
>
> array_upper(a || b) == array_upper(a) + CARDINALITY(b)
>
> and would work just fine. Note that if array-a is NULL, then the spec defines a
> || b as NULL. See section 6.35:
Why are you talking about when a is NULL? The ori
Greg Stark wrote:
length(a) != array_upper(a)-array_lower(a)
[You really meant "array_upper(a) - array_lower(a) + 1" I'd guess]
length(A) is a missing function at the moment; the spec actually calls
it CARDINALITY. Once available, you would use it to determine array
length. SQL2003 says:
The
Hello folks,
just wanted to mention that the first part of the slovak
translation of Pg is available - the psql strings - at the following
address:
http://de.geocities.com/bartkozo/psql-sk.po.gz
It is the 7.4 branch/newer.
Thanks for reading
Zoltan
"J. Andrew Rogers" <[EMAIL PROTECTED]> writes:
> I may be completely missing the point here, but it looks to me as though
> the PITR archival mechanism is also most of a native replication
> facility. Is there anyone reason this couldn't be extended to
> replication, and if so, is anyone plannin
Josh Berkus <[EMAIL PROTECTED]> writes:
> Joe,
>
> > This is correct. There are no dimensions to an empty array by
> > definition. The only other way to handle this would be an ERROR. I
> > followed the lead of (the pre-existing function) array_dims() when
> > creating array_upper() and array_
Joe,
> Sure, and in both cases array_upper is undefined because there are no
> array dimensions to speak of. I guess you might argue that array_upper,
> array_lower, and array_dims should all produce an ERROR on null input
> instead of NULL. But that would have been an un-backward compatible
>
Josh Berkus wrote:
What about a 0?That seems more consistent to me. If the array
is empty, its dimensions are not "NULL", meaning "unknown", but in
fact zero elements, which is a known value.
They cannot be 0 because 0 is a real index. They are undefined, because
an empty array has no dimens
On Fri, 1 Apr 2004, J. Andrew Rogers wrote:
>
> I may be completely missing the point here, but it looks to me as though
> the PITR archival mechanism is also most of a native replication
> facility. Is there anyone reason this couldn't be extended to
> replication, and if so, is anyone planning
Joe,
> This is correct. There are no dimensions to an empty array by
> definition. The only other way to handle this would be an ERROR. I
> followed the lead of (the pre-existing function) array_dims() when
> creating array_upper() and array_lower().
What about a 0?That seems more consiste
I may be completely missing the point here, but it looks to me as though
the PITR archival mechanism is also most of a native replication
facility. Is there anyone reason this couldn't be extended to
replication, and if so, is anyone planning on using it as such?
My memory is fuzzy on this point
Josh Berkus wrote:
I'm noticing some inconsistent behavior regarding empty arrays and IS NULL
status.For example:
net_test=# select array_upper('{}'::INT[], 1) IS NULL;
?column?
--
t
(1 row)
This is correct. There are no dimensions to an empty array by
definition. The only other wa
Hi,
[Just so y'all know: This has been discussed extensively in
#PostgreSQL and I tried asking the question in both -admin and
-general, first. Also did some web searching.]
Environment:
PostgreSQL 7.4.2
Locally built with GCC 3.3.1
Solaris 8 (Sparc)
I have a relatively simple d
I am trying a pre-load a user table during InitPostgres. I tried to mimic
the relevant actions in ReverifyDatabase to carry this out. I manage to
load the first block of the table. However, if a table is more than 1
block, I end up getting warnings about relcache reference leaks. It looks
Last link was wrong.
Here's the correct one.
http://www.dertech.com/pgmex/pgmex.html
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Fabien COELHO <[EMAIL PROTECTED]> writes:
> Sure:-)
> Subject: [PATCHES] hint infrastructure setup (v3)
Oh, I was intending to review that but got caught up in functions-
returning-rowtypes hacking. I'll take a look as soon as I'm done
with the rowtypes project (should be in a day or two).
Dear Bruce,
> > BTW, maybe you could reject some of the patches I submitted earlier,
> > rather than to simply ignore them?
>
> The only outstanding patch I see from you is:
>
> [PATCHES] [NOT] (LIKE|ILIKE) (ANY|SOME|ALL) (subquery...)
>
> from March 29. I will put it in the queue now. Ar
Fabien COELHO wrote:
>
> Dear Tom,
>
> > > So my question still is: Given the fact that I have some use for these
> > > oids, would it make sense to submit a patch to add them?
> >
> > It will be rejected.
>
> That's a simple a direct answer as I like them.
> So I won't bother to submit a patch;
Dear Tom,
> > So my question still is: Given the fact that I have some use for these
> > oids, would it make sense to submit a patch to add them?
>
> It will be rejected.
That's a simple a direct answer as I like them.
So I won't bother to submit a patch;-)
BTW, maybe you could reject some of t
DerTech LLC has developed a MATLAB interface for PostgreSQL. It's
essentially mex wrappers for the functions in libpq. We're releasing
it for free with source code included.
Here's the website link: http://www.dertech.com/neurodb/pgmex.html
Could this be added to the related projects page?
Thank
22 matches
Mail list logo
