I have experience with LLBL Gen 1.0.x and am now helping a coworker who has the new 3.1 version of LLBL and I am at a loss for an explanation on something...

-Database Oracle 11g -Adaptor mode -llbl gen 3.1

We generate the code initially fine and queried alright, then hit the issue with Oracle sequences on inserts (trigger driven) that I used to hit with version 1.0.X.

We looked into the designer for the way to set the sequence. So far I believe we have used the automapping (is this default)? Next, I found the field mapping tab and saw that you could manually set the database field mapping which lead to the the ability to specify a sequence to use (after a refetch during runtime). Great. However, the code generator now complains that all of the other entities are not mapped.

Manually mapping the rest of the entities seems to make them no longer an issue for code generation. We did not have to have any mappings done in the "field mappings" tab prior for this project. Am I missing something? Are the mappings for the other entities no longer automatic, once one entity is manually mapped to a database within our project?

Thanks.

Hi there,

Since v3.x, there are two main concepts when you work in your project: DB First and Model First. Please read this to understand them.

I don't know if you started with DB-First or Model-First. If you do DB-First, all is mapped automatically. If you started Model-First you need to map entities and fields, but you can just right-click the root project node and select to automap everything.

Thanks. I have been enlightened.

Actually, what had happened was we in the process of other things deleted the schema from the llbl project which removed all of the mappings. Minor detail, I know. (sarcasm)