Re: rounding problems

From: Justin <justin(at)emproshunts(dot)com>
To: Andy Anderson <aanderson(at)amherst(dot)edu>, pgsql-general(at)postgresql(dot)org
Subject: Re: rounding problems
Date: 2008-05-14 20:55:49
Message-ID: 482B51D5.9080001@emproshunts.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andy Anderson wrote:
>> Sam Mason wrote:
>>> If you mean FoxPro, I think this is another case of MS screwing up.
> On May 14, 2008, at 4:08 PM, Justin wrote:
>> Foxpro normally did not suffer form other MS screw ups.
> That's because MS bought it from a third-party developer.
> (And so, of course, they couldn't allow that to stand, and had to develop their own product, Access. What a hunk of junk that was for the first couple of years. :-(
> -- Andy
>
I loved foxpro its the best Xbase language. MS killed because they did
not want to move it to 64 bit. Which would have made all the
limitations that it suffered from due to 32 integer go away.

What annoys me everyone told me how crappy xbase languages were/are but
today most of the popular programming languages are now just getting
tools that we Xbases developers have had forever.

Don't get me started on the Access Jet Engine blue or red. They both
suck and prone to failure. I still have a hard time believing MS uses
Jet Engine Blue for Exchange and AD. I have spent allot time
recovering from corrupt databases. And the way MS shoe horned Exchange
into that flawed database design is amazing.


In response to

Browse pgsql-general by date

  From Date Subject
Next Message George Pavlov 2008-05-14 21:20:00 DB page cache/query performance
Previous Message Matthew T. O'Connor 2008-05-14 20:52:39 Re: PG -v- MySQL