I've been investigating OpenAccess ORM for a particular project that I'm about to start work on. I've spent some time looking at nHibernate too so as to understand the differences between the two and come up with a judgement as to which one to recommend. One of the major problems with the reverse mapping that we will ultimately have to do is that the database design we are working against has some significant drawbacks.
One of the most pressing areas is around id generation for a given table and I'll explain why. The database design that I'm stuck with means that the primary key id for a given table is usually defined but the corresponding auto-increment property generally isn't. The id comes from a "sequence" (of sorts) - with the value for the next item retrieved using a stored procedure. nHibernate can handle this as within the mapping file for a given class you can specify a custom id generator within a given id mapping and by writing a class that implements IIdentifierGenerator and IConfigurable the rest is relatively easy. My question is this: is this kind of thing possible with OpenAccess ORM and if yes how?