Hi,

Looks like one can't use sequences in DBs that have a secondary DB.
This may or may not be reasonable, but it would be a good idea to
mention it in the docs or have a better error message. Right now it's
giving an "Invalid Argument Exception" with a 'null' detail message.

this is with 4.3.29

Best,
Boris

Hi Boris,

This is kind of a strange thing to do -- how do you expect to look up
the sequence from the secondary index?

As far as I know, it is possible to put a sequence in a primary
database, but your secondary key callback needs to know about it and
either not generate a secondary key (by returning false in the Java
API), or by generating a secondary key solely on the basis of the
primary (not using the sequence data).

What is giving this exception? What operation is your application
performing when the exception occurs? What does your
createSecondaryKey method do? What does the stack trace look like?

Regards,
Michael.

To be honest, I'm not expecting anything from the secondary index. I
didn't think I needed to worry about it. The way the API is defined,
one is led to believe that there's not interference b/w the main data
and the sequences associated with the DB.

The exception is thrown by the Database.openSequence method. It is not
thrown when a secondary database is not created.

So the proper/safe way would then be to create a "sequences" table in
an environment...

Thanks,
Boris