Hackers,
One can alter a user to set a validity timestamp. However, unless one
uses the ugly kludge of setting a date very far into the future, there's
no way to set this validity forever.
Should I make a patch to correct this? Should be quite trivial.
--
Alvaro Herrera ()
"El dia que dejes d
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Some people were mentioning an error message style guide. Here's a start
> of one that I put together a while ago. Feel free to consider it.
Looks like a good start. But you expected quibbles, right? ;-)
> The main part of a message should be at
On Fri, Mar 14, 2003 at 14:19:46 -0600,
Taral <[EMAIL PROTECTED]> wrote:
> Same setup, different query:
>
> test=> explain select max(time) from test where id = '1';
> NOTICE: QUERY PLAN:
>
> Aggregate (cost=5084.67..5084.67 rows=1 width=0)
> -> Index Scan using idx on test (cost=0.00..50
Justin Clift wrote:
[ ... ]
The problem Dave is suggesting this as a first attempt at a solution for
is that with ODBC, a frontend (i.e. OpenOffice) asks the ODBC driver
which columns are NULLable, etc. And the ODBC driver is getting the
info wrong, then passing back the incorrect info.
And t
