This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi Guys,
We've got a problem here with table name pluralisation. We have a table called LookupData in our domain model. Every time when we do an Update From Source in LightSpeed designer, it automatically change it to LookupDatum. This is really annoying, anyone can kindly point out what we've done wrong. Any help is appreciated. Thanks in advance. Nathan |
|
|
You could try setting the Table Name in the designer to LookupData: I'm not optimistic it will work but it would be quick and easy to test. However, if the model is not yet set in stone, I would advise renaming both the table and (at minimum) the entity to something more specific. As a cheap kludge, changing the entity name to be different from the table name should mean that setting the Table Name ought to work! But there are good domain model reasons to change the name anyway. A Data suffix on a class name is generally redundant, and can be confusing because it's not clear whether it's plural (i.e. an object represents a data set) or singular (a object represents a single datum, e.g. a single lookup item). (This is why LightSpeed changes Data to Datum: to make it clear that it is a single item.) If you want to use a generic suffix, Item or Info might be clearer. It might also be useful to use a more specific term than Lookup -- e.g. what is being looked up? Configuration entries? Display metadata? Country details? After all, one day you might have a second table containing a different kind of reference data... If changing the entity name really isn't an option (and if you're on a nightly, don't forget you can now do a solution-wide rename using the Refactor menu), let us know and we'll see what we can do. |
|