rblock wrote:
Hi Frans,
Otis wrote:
Make sure 'Enforce Pascal casing always', and 'Make element name pascal casing' are checked, then re-create the entities.
I did it, not the entities in LLBL where uppercase. ORACLE stores all names in uppercase. I switched on this Pascal casing but what shall the LLBL do? It does not know the words therefore just the first character is uppercase and the rest lowercase.
It checks for word breaks. If all names are uppercase, you likely have underscores in the names as well, like CUSTOMER_ID, or COMPANY_NAME. It will convert those to CustomerId and CompanyName. If there are no _ on wordbreaks, then indeed it doesn't know.
It's common practice on oracle to use underscores to make names more readable. If everything is uppercase and no underscores are used, things are unreadable if they get longer. But I don't know whether your system has this or not.
Otis wrote:
Because the tree is updated at most once a second.
When U right click on a leaf and change the name in the dialog that appears and press the OK button, just in this moment the tree is rebuild.
Over here I attached a small screenshot with a naming example, what happens during import with uppercase names and camelcase switch on.
Ok. I can reproduce it now. Btw, rename navigators below the entity, not below the relationship. It works OK, but the relationship is removed and re-added, so it's going to be collapsed afterwards. Just rename the navigators, which is easier.
It re-adds the nodes, (as they're re-sorted, a name change can cause that the names have to be resorted), and doesn't set focus back onto the node which was focused last. The main issue is that the old nodes which were 'selected' are now gone, new nodes (with the same, or different text) are re-added.
We'll see what we can do, but I can't promise anything...