headache
2. Blobs would not be restored
--
Regards,
Vishal Kashyap
Director / Lead Software Developer,
Sai Hertz And Control Systems Pvt Ltd,
http://saihertz.rediffblogs.com
Yahoo IM: mailforvishal[ a t ]yahoo.com
---(end of broadcast)---
TIP 9:
for any kinda answers.
--
Best Regards,
Vishal Kashyap
Director / Lead Developer,
Sai Hertz And Control Systems Pvt Ltd,
http://saihertz.rediffblogs.com
Jabber IM: [EMAIL PROTECTED]
ICQ : 264360076
---
You yourself, as much as anybody in the entire
Dear all ,
Would like to receive your kind attention and enormous knowledge on the
following
I have a function
sai_func_a()
Which does as follows and in the same order:
1. Retrieves the latest record from the table test_sai
(By latest I mean the record corresponding to max primary key o
Dear Lamar Owen ,
Since we are keeping
all source releases (although I would question that, since we use CVS),
keeping all the binaries around is just a space waster, IMHO.
Comments?
Keeping 7.X and then 7.X.y where y is the last minor version for 7.X is
fine
As you would have noticed from
Dear Jan Wieck ,
Yes I agree with you Jan , most of the time we round the amount and
this is done by truncating greater than 3 decimal digits and
rounding the 3 digit to 2 in other words :
select trunc(1000.236897,3);
then
selecr round(1000.236,2);
This takes care of the rounding factor in m
Dear Jan Wieck ,
Floating point math itself is not precise, but rather an approximation,
usually of 8 or 14 digits. You can't approximate money. This isn't a
PostgreSQL issue but rather a general programming issue.
Thanks, Bruce. I assume the arbitrary precision arithmetic Jan
mentioned which
Dear all ,
I would like to share my concerns about the IEEE 754 specification and
floating point handling by PostgreSQL .
Also I would like to learn how professional users of PostgreSQL work
with rounding of monetary terms .
If you would like to know whats IEEE 754 read this
http://docs.sun
