- This topic has 1 reply, 2 voices, and was last updated 11 years, 7 months ago by
.
-
When eaDocX accesses the EA repository directly – which it has to do because there aren’t the required APIs in EA – it uses upper-case table names. This works OK in all the major DBMSs, when they are configured normally. We’ve tried it with SQLServer, Oracle, MySQL and EAP files.
BUT, we know that it is possible to configure some DBMSs so that they are case sensitive, so, we issue SQL to look at T_OBJECTS, and it only has a t_objects table.
We have so far not found a pattern to when this happens, and it would be a MAJOR change to eaDocX to allow for case-sensitive SQL, as we will have to parse the results in mixed case as well.
So, have a look at the case sensitivity of your DBMS.
Also, EA itself seems to be OK with this, it’s just SQL issues via EA which has the problem.
- You must be logged in to reply to this topic.
Download a free trial
Download eaTeamWorks today for free for life features, plus no obligation, 30-day trials of all the products: eaDocX, Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why eaTeamWorks is the world’s best-selling Enterprise Architect extension.
Download