Attribute named "ID" causes error in SQL alchemy generator

[Aran30]

If a model contains a class with an attribute named "ID", this will generate sql alchemy code containing an error. The problem stems from the sql alchemy generator always adding a column named "id" as a primary key, thus leading to a table having two columns named ID. The sql alchemy generator needs to do an additional check for attributes called "id".

[jcabot]

We should also add a configuration property to configure whether we want to generate these ID fields for every class or not (I think we already have something similar for another generator)

[ivan-alfonso]

This issue is now fixed. If a model contains a class with an attribute named id, that field will be used as the table's primary key. Otherwise, a default id field will be created for the table.

Additionally, if an attribute of a class is marked as is_id, that field will be set as the primary key of the table.