Would be nice if Entity Modeler would prevent or at least show a warning if someone uses a reserved keyword for entities/attributes.
I mean names that conflict with database keywords as "select", "alter", ...
These two are apparent to be bad names for a model but some may be not and these could be potentially a source of error in SQL execution.
I had one case some time ago where I had a conflicting name in FB (I think it was using "User" for a table name) and I had some erratic behaviour (I had never to do with SQL before so it took quite some time to get hold of the error).
Had an eomodel with an attribute 'left' that caused an exception during migrations for postgresql. Same thing for 'right'.
Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near "left"
Reported by Johann Werner
Would be nice if Entity Modeler would prevent or at least show a warning if someone uses a reserved keyword for entities/attributes.
I mean names that conflict with database keywords as "select", "alter", ... These two are apparent to be bad names for a model but some may be not and these could be potentially a source of error in SQL execution.
I had one case some time ago where I had a conflicting name in FB (I think it was using "User" for a table name) and I had some erratic behaviour (I had never to do with SQL before so it took quite some time to get hold of the error).
Had an eomodel with an attribute 'left' that caused an exception during migrations for postgresql. Same thing for 'right'.
Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near "left"