JT Kirkpatrick <[EMAIL PROTECTED]> writes:
> we made all monetary fields FLOAT4's. weird stuff -- or maybe not to you
> -- we insert 23516.69 into a float4 field directly in psql, and then select
> it, and it shows 23516.7. this is not good for a field used for MONEY!!!
Yup, no surprise. fl
We ran into a problem with some tables that were taking forever to
vacuum due to the indices we had created. The trick of dropping the
indices and recreating them after the vacuum works very well, so I
looked for a way to automate it. Here's what I came up with. I call
it "autovac".
It process
You shouldn't use a float at all for exact amounts. Floats handle
arbitrary precision, but do it rounding off values somewhat. The way the
round off works is based on the (base 2) internal representation and so
it never quite seems to make sense in decimal. It's possible on some
machines/float f
we have a database (linux, 6.4.2, new odbc, connections from msaccess /
win98) -- access doesn't fully appreciate the monetary type in postgres, so
we made all monetary fields FLOAT4's. weird stuff -- or maybe not to you
-- we insert 23516.69 into a float4 field directly in psql, and then sele
bomb = lock up most other users. some can still get in and view things.
seems like only rarely does it lock up direct access through psql.
ps ax shows some update and other selects waiting. you can kill those and
it doesn't help. in fact, you can kill each process (or user) in postgres
an
At 11:06 +0300 on 28/06/1999, Rudy Gireyev wrote:
> This may be slightly more reasonable. :-)
> But ideally one would like to say:
> SELECT * from chargehistory WHERE "new" is TRUE;
>
> No? :-)
If you are into semantics, I don't really think so. You say things like "If
unsure, ask an expert", n
On 28 Jun 99, at 9:24, Ansley, Michael wrote:
> >>> If I may add, I always found the practice of comparing boolean values
> to
> >>> "true" or to "false" rather funny. You take a boolean value, and
> compare it
> >>> to 'true'. You get a boolean result that is the same:
> >>>
> >>> Truth ta
>>> If I may add, I always found the practice of comparing boolean values
to
>>> "true" or to "false" rather funny. You take a boolean value, and
compare it
>>> to 'true'. You get a boolean result that is the same:
>>>
>>> Truth table of "new" = 't':
>>>
>>> newnew = true
>>>
