Bugs item #2818176, was opened at 2009-07-07 19:38
Message generated for change (Comment added) made by nielsnes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2818176&group_id=56967

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: SQL/Core
Group: MonetDB5 "stable"
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Franck Routier (alci)
Assigned to: Niels Nes (nielsnes)
Summary: NUMERIC data type not following sql standard

Initial Comment:
The numeric type in Monetdb has two shortcomings :

- numeric is an arbitrary precision number. Imposing a limitation of 18 digits 
in the implementation is a bit restrictive (it is ok, but most rdbms will have 
much higher precision)

- when defining the type NUMERIC(P,S), P+S must be <= 18. But in fact, P should 
be the total number of digits, so if the limit is 18, we should have P <= 18 
(and of course S<P)

----------------------------------------------------------------------

>Comment By: Niels Nes (nielsnes)
Date: 2009-07-20 18:44

Message:
could you please add the failing prepare/execute statements (including ddl
statements). Its hard to reproduce bugs without test scripts.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2818176&group_id=56967

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs

Reply via email to