cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <>
Subject [jira] Commented: (CAY-1188) Add method that lists "bad names" and show warning in Cayenne modeler
Date Mon, 11 May 2009 13:07:45 GMT


Andrus Adamchik commented on CAY-1188:

>From MSSQL docs mentioned above: "Although it is syntactically possible to use SQL Server
reserved keywords as identifiers and object names in Transact-SQL scripts, this can be done
only using delimited identifiers."

Not sure if by "delimited" they mean "quoted", but coincidentally upcoming 3.0M6 supports
optional quoting of identifiers. So it can potentially handle arbitrary DB names.

> Add method that lists "bad names" and show warning in Cayenne modeler
> ---------------------------------------------------------------------
>                 Key: CAY-1188
>                 URL:
>             Project: Cayenne
>          Issue Type: New Feature
>          Components: Cayenne Core Library
>    Affects Versions: 3.0M5
>            Reporter: √ėyvind Harboe
>            Assignee: Andrey Razumovsky
> When creating database models directly in Cayenne, there are names for fields which are
incompatible with databases. E.g. naming a field "file" works fine in Derby, but fails in
MS SQL server.
> It would be nice if the modeler gave a warning about such bad namechoices. 
> In addition to a global list of bad names, each adapter could ammend names that probably
shouldn't be used.
> The main problem is that such bad name choices will only be deteced upon deployment,
so testing against Derby and deploying against MS SQL/Oracle can cause unecessary headaches.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message