LLBLGen renames table

Posts   
 
    
Rlaan avatar
Rlaan
User
Posts: 14
Joined: 21-Apr-2017
# Posted on: 31-May-2017 11:00:38   

Hello,

Using: LLBLGen version 5.1 (5.1.3) RTM with the LLBLGen Pro Runetime Framework. MSSSQL database version 2014, and the 4.5.2 .NET Framework, SelfServicing.

Currently I'm a bit confused by why LLBLGen is renaming my table, I have two tables, one called: AgendaEvent, and one called AgendaEventMeta. The only thing is, once I "reverse-engineer Tables to Entity Definitions" the table AgendaEventMeta is being renamed to AgendaEventMetum and I have to manually change it to Meta.

Any idea what might be causing it? Or is it a similair problem like I had in thread: http://llblgen.com/TinyForum/Messages.aspx?ThreadID=24266 due to LLBLGen using the keyword?

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 31-May-2017 19:43:05   

That's the default Naming Singularization, you can disable it, as described here

Also there is a Project Setting called "Singularize element names", under Reverse Engineering section. Which when set to true (default), the name for a new model element which is derived from the relational model element (e.g. table) it is reverse engineered from, is singularized. Example: a new entity reverse engineered from the table Customers will be called Customer.

Rlaan avatar
Rlaan
User
Posts: 14
Joined: 21-Apr-2017
# Posted on: 01-Jun-2017 10:05:40   

Walaa wrote:

That's the default Naming Singularization, you can disable it, as described here

Also there is a Project Setting called "Singularize element names", under Reverse Engineering section. Which when set to true (default), the name for a new model element which is derived from the relational model element (e.g. table) it is reverse engineered from, is singularized. Example: a new entity reverse engineered from the table Customers will be called Customer.

That makes sense, thanks I'm going to look into it. But it's good to know that it won't cause any conflict with llblgen simple_smile thanks.