On 2 Aug 2010, at 23:43, Radosław Smogura wrote:
PostgreSQL already has BIGINT aka INT8, which are 8 bytes, and can
represent integers up to like 9 billion billion (eg, 9 * 10^18).
But I think about numbers with precision - you can use float for moneys, etc
(rounding problems), and dividing
Usually bighouse financial systems use BIGINT and a field to store
position-of-decimal point to track arbitrary precision currency values...
That's the right way to do it. I believe for mom-and-pop stuff, you can
satisfy the auditors if you use NUMERIC(,2) and implement round-to-even
(banker's
Hello,
I'm not member of this list, but because the 9th version of PostgreSQL is
incoming, I would like to ask if there is possibility to add session
property of application user - this property, in contrast to login name,
should be setted by driver (e.g. JDBC) to current user logged into
On Mon, Aug 2, 2010 at 07:30, rsmog...@softperience.pl wrote:
Hello,
I'm not member of this list, but because the 9th version of PostgreSQL is
incoming, I would like to ask if there is possibility to add session
property of application user
Not for 9.0 its more or less already cut.
- this
On 08/02/10 6:30 AM, rsmog...@softperience.pl wrote:
I would like to ask, about your opinion about numeric type. I implemented
binary read for numeric type in JDBC and I saw, that numeric type is stored
inside database as array of shorts no greater then nbase (currently 1).
In my opinion
how would you handle scale factors? numeric represents a BCD data
type, with a decimal fractional component. how would you represent,
say, 1.001 in your version? how would you add 1.001 to 1.01
in your binary representation?
I think about datastructure something like this
