This seems to be effective even when manually changing a field name in the designer.

I would like see this be used only when retrieving new fields (initial and new fields in subsequent refreshes) and allow a manual change to be unaffected.

Cheers Simon

PS The workaround is of course to set the value to false, make the changes, and then set it back to true but this is a pain.

The question then is of course, why you would want pascal cased names when retrieving the meta data from the db but not when you type it in manually?

Otis wrote:

The question then is of course, why you would want pascal cased names when retrieving the meta data from the db but not when you type it in manually?

Thats easy - the vast majority of names should be changed pascal case but some I require to be as I type them in. For example I prefer "ID" to "Id".

Its very disconcerting to change something and then immediately have the change removed. I see the option as a best guess for initial setup, which is correct in the vast majority of cases, but may require some manual tweaking.

(In an ideal world, I would like to see a way of being able to specify some rules for choosing a field name. In the project I am currently working on, I didn't have any input on the column naming conventions and it would be great to be able to replace "_dtm$" (regex) with "Date" (yes someone really decided to use _dtm as a suffix for all date time columns!)) .

Cheers Simon

simmotech wrote:

Thats easy - the vast majority of names should be changed pascal case but some I require to be as I type them in. For example I prefer "ID" to "Id".

I too like my ID instead of Id... It would be nice to be able to change the hard coding of the names...

I see your points, so you want a setting where names are corrected during schema imports, but not when the user manually alters names?

Otis wrote:

I see your points, so you want a setting where names are corrected during schema imports, but not when the user manually alters names?

Spot on!

Cheers Simon

simmotech wrote:

Otis wrote:

I see your points, so you want a setting where names are corrected during schema imports, but not when the user manually alters names?

Spot on!

Cheers Simon

I'm loving this tool more and more... and I'm filled with anticipation for V2

UPDATED:

Is it possible to get a hotfix for this feature?

C4 wrote:

simmotech wrote:

Otis wrote:

I see your points, so you want a setting where names are corrected during schema imports, but not when the user manually alters names?

Spot on!

Cheers Simon

I'm loving this tool more and more... and I'm filled with anticipation for V2

UPDATED:

Is it possible to get a hotfix for this feature?

Well, it's not that easy to implement I think. The problem is that every routine which deals with names uses a central routine which validates the names, so to tell it when to ignore which rules will be more complex than just a flip of a switch

+1 for this exact feature. Hate "Id", love "ID".

This is implemented in v2.0