On Thu, 2004-01-01 at 22:20, Tom Lane wrote:
My object is to get 7.4.1 working on all the Debian architectures.
I'd have been more willing to buy into that goal if you'd been working
on it during the 7.4 beta test cycle. I gather from what you are saying
that you couldn't, because Debian
Where is the standard, I for one would be interested in seeing it?
Dave
On Fri, 2004-01-02 at 01:09, Andrew Dunstan wrote:
Jan Wieck wrote:
The basic question is the definition of the lifetime of an object and
it's identificaition when doing nested calls in this context. In the
OO
Dave Cramer said:
Where is the standard, I for one would be interested in seeing it?
AFAIK it is not available except for $$$. It looks like the relevant
standards are parts 1 and 2 of the SQLJ standard (Part 0 covers embedded
SQL).
cheers
andrew
---(end of
Jan Wieck [EMAIL PROTECTED] writes:
Tom Lane wrote:
Another little problem is that plpgsql doesn't really have any mechanism
for invalidating cached stuff at all; it will leak memory like there's
no tomorrow if we start dropping cached subplans.
Everyone seems to look at it as a PL/pgSQL
Jan Wieck [EMAIL PROTECTED] writes:
Tom Lane wrote:
No, of course not, but plpgsql has issues of its own that (IMHO) should
be solved along with the SPI-level problem.
Not sure what you mean by that.
I'm referring to the fact that plpgsql's internal data structures are
all built with malloc
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
Tom Lane wrote:
Another little problem is that plpgsql doesn't really have any mechanism
for invalidating cached stuff at all; it will leak memory like there's
no tomorrow if we start dropping cached subplans.
Everyone seems to look at it as a
On Thu, Jan 01, 2004 at 11:19:07PM -0500, Eric B.Ridge wrote:
I couldn't think of a way to create a whole new database type for
Xapian that could deal with managing 5 btree indexes inside of Postgres
(other than using tables w/ standard postgres btree index on certain
fields), so instead,
Dave Cramer wrote:
Barry,
Ok, so if we drop this limitation then we leave it up to the architect
to manage the caching problem themselves.
Maybe I don't understand enough about Java, but isn't this limitation
(only static methods callable) exactly what avoids having to deal with
the
Andrew Dunstan wrote:
AFAIK it is not available except for $$$. It looks like the relevant
standards are parts 1 and 2 of the SQLJ standard (Part 0 covers embedded
SQL).
For working drafts try:
http://www.wiscorp.com/sql/sql_2003_standard.zip
(5WD-13-JRT-2003-09.pdf)
Create table with type TIMESTAMP(0)
Chris
ivan wrote:
how can i change default time format because now i have for example
2004-01-01 16:51:46.995927 but i want only 2004-01-01 16:51:46, with out
millisec. a tryed with Data-Style but there arent custom style :/
---(end
10 matches
Mail list logo
