Nectari Demandes d'amélioration

I found that quite often the tables/views and field names in the database need to be changed after they are already used in the Nectari data models.

The main reason is that the approach to structuring of the database objects (tables and views) may change as the report development progresses and requirements get rectified and/or amended. This also may also happen when re-factoring the legacy code.

If I change a field name in the table/view, it just appears as a new field, and the old one disappears (which obviously triggers all sorts of errors).

I wanted to ask for a possibility to configure the relation between the database objects and SEI Data models.