Sequence's current value advances to next 100 upon reconnection in derby
I am having an issue with derby sequences with embedded database. When I first connect to the data base it gives me the correct sequence next value with the following statement. VALUES (NEXT VALUE FOR :seqNm) But when restart my desktop application, there by reconnecting to the database, the next value gives me the next hundredth value. It seems like derby uses some caching for preallocating the sequence numbers. e.g. if my sequence starts with 100, First connection to the data base gives me sequences as 100, 101, 102 and so on. Second connection to the data base gives me sequences as 200, 201