Franco,
> Wouldn't it be the most portable solution to work with a domain?
> CREATE DOMAIN BIG_NUMBER AS BIGINT;
>
> If I use BIG_NUMBER everywhere I need it in my database, porting it to
> other database products should be easy... any SQL 92 compliant dbms
> should support domains.
This is a goo
On Saturday, September 27, 2003, at 10:39 PM, Yusuf W. wrote:
Now, I've got to convince my project's software
architech, that a bigint would be better than a
decimal.
Does anyone know where I could get some documentation
on how the int and decimal are implemented so I could
prove to him that ints
Wouldn't it be the most portable solution to work with a domain?
CREATE DOMAIN BIG_NUMBER AS BIGINT;
If I use BIG_NUMBER everywhere I need it in my database, porting it to other database products should be easy... any SQL 92 compliant dbms should support domains.
On Sun, 2003-09-28 at 00:06,
Yusuf,
> Does anyone know where I could get some documentation
> on how the int and decimal are implemented so I could
> prove to him that ints are better? Can people suggest
> good points to make in order to prove it?
RTFM:
http://www.postgresql.org/docs/7.3/interactive/datatype.html#DATATYPE-N
Now, I've got to convince my project's software
architech, that a bigint would be better than a
decimal.
Does anyone know where I could get some documentation
on how the int and decimal are implemented so I could
prove to him that ints are better? Can people suggest
good points to make in order
"Yusuf W." <[EMAIL PROTECTED]> writes:
> For the application that I'm working on, we want to
> use data types that are database independent. (most
> databases has decimal, but not big int).
Most databases have bigint, I think.
> Anyhow, we are planning on using decimal(19,0) for our
> primary ke
