Bugs item #2846238, was opened at 2009-08-28 09:38 Message generated for change (Comment added) made by matburt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2846238&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Matthew W. Jones (matburt) Assigned to: Niels Nes (nielsnes) Summary: alter sequence restart on large integer Initial Comment: I believe I may have found a bug in the sequence though... I want to make sure that this value will not have problems when working with large integers: sql> CREATE SEQUENCE "test_seq" as bigint; sql> select next value for test_seq; +------------------------------+ | next_value_for_testdb | +==============================+ | 1 | +------------------------------+ sql> alter sequence test_seq restart with 3000000000; sql> select next value for test_seq; +------------------------------+ | next_value_for_testdb | +==============================+ | 2147483647 | +------------------------------+ I can always increment the sequence higher, but if I try to alter it to anything past the maximum value for a 32-bit integer then it will reset to it. sql>select next value for test_seq; +------------------------------+ | next_value_for_testdb | +==============================+ | 2147483648 | +------------------------------+ 1 tuple sql>select next value for test_seq; +------------------------------+ | next_value_for_testdb | +==============================+ | 2147483649 | +------------------------------+ ---------------------------------------------------------------------- >Comment By: Matthew W. Jones (matburt) Date: 2009-08-28 11:29 Message: I'm actually doing this outside of an auto increment or serial field in a table.... I'm just strictly creating, querying, and altering the sequence. Looking in the 'sequences' table shows that all of its integer fields are bigints.... it also seems to increment past a 32-bit integer.... the error must be in the code that takes the new value during the sql query for 'alter sequence restart ...' ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2009-08-28 10:03 Message: This might actually be a bug related to serial being a INT, not a BIGINT. We should probably implement bigserial, and fix the sequence code here not to accept the too large value. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2846238&group_id=56967 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
