You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrey Razumovsky (JIRA)" <ji...@apache.org> on 2009/03/10 10:00:17 UTC
[jira] Commented: (CAY-1188) Add method that lists "bad names" and
show warning in Cayenne modeler
[ https://issues.apache.org/cayenne/browse/CAY-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273#action_13273 ]
Andrey Razumovsky commented on CAY-1188:
----------------------------------------
Sounds reasonable, and quite easy to implement. You are encouraged to make a list of "bad" names to speed up the process
> Add method that lists "bad names" and show warning in Cayenne modeler
> ---------------------------------------------------------------------
>
> Key: CAY-1188
> URL: https://issues.apache.org/cayenne/browse/CAY-1188
> Project: Cayenne
> Issue Type: New Feature
> Components: Cayenne Core Library
> Affects Versions: 3.0M5
> Reporter: Øyvind Harboe
>
> 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.