Custom property 'MS_Description' in every refresh of SQL Server DB

Posts   
 
    
kakaiya
User
Posts: 161
Joined: 20-Mar-2004
# Posted on: 27-Oct-2011 07:26:09   

Hi,

Everytime when code is generated it shows below lines for each columns in DB.

Using SQL 2005, LLBLGen v3.1 June 17th, 2011, c#, .NET 4.0, Adapter.

Custom property 'MS_Description' of 'SQLServerFieldNameHere' updated with new value from mapped element.

Any idea?

Kakaiya

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 27-Oct-2011 10:58:47   

So, you don't want to fetch or update database custom properties?

kakaiya
User
Posts: 161
Joined: 20-Mar-2004
# Posted on: 28-Oct-2011 04:56:14   

Hi,

Whenever the database schema refresh is done - need latest MS_Description from SQL Server DB.

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 28-Oct-2011 10:45:01   

Please execuse my confusion.

Custom property 'MS_Description' of 'SQLServerFieldNameHere' updated with new value from mapped element

Where do you see this line? And is it on DB refresh as the title says, or on code generation as the message body says?

kakaiya
User
Posts: 161
Joined: 20-Mar-2004
# Posted on: 29-Oct-2011 12:18:10   

Hi,

Open the LLBLGen project file in editor, then perform a DB refresh and in the resulting window you can see as per below.

Relational model data refresh results Refresh results Migration of project elements to new catalogs

Entity 'ENTITY_NAME' Entity migrated to target 'dbo.TABLE_NAME'. Custom property 'MS_Description' of 'FIELD_NAME' updated with new value from mapped element. ... ... ...

ANOTHER QUERY: Why after every DB refresh it shows these messages?

Custom property 'MS_Description' of 'FIELD_NAME' updated with new value from mapped element.

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 30-Oct-2011 23:59:47   

Those messages are shown after refresh as a log of what the refresh process did. In the case of custom properties, these are the relevant Preferences/CustomProperties:

RetrieveDBCustomProperties When set to true, all custom property data of the database objects a new project object is based on will be copied to the object's Custom Properties.

**UpdateCustomPropertiesAfterRefresh **When set to true, any custom property in an entity, entity field, typed view, typed view field or stored procedure will be updated with a similar named custom property in the newly catalog information, after a refresh of the catalog(s). Setting this option to true can break your own code, so use this option with care. If you have set RetrieveDBCustomProperties to false, this option has no effect. The value Default means the value in the preferences is used.

So, do you want the custom properties retrieved to your model? Do you have those flags on?

David Elizondo | LLBLGen Support Team
kakaiya
User
Posts: 161
Joined: 20-Mar-2004
# Posted on: 31-Oct-2011 05:20:28   

Hi,

Yes, both flags set to true (RetrieveDBCustomProperties and UpdateCustomPropertiesAfterRefresh)

After doing a DB refresh, it shows in Refresh Results window what are the field changes in tables.

It always shows all 'MS_Description' regardless of it is changed or not.

Is this correct?

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 31-Oct-2011 11:42:24   

Yes, it doesn't do value change checking, it simply reflects whether it has set the value or not, to tell the user that a value was found in the relational model data.

Frans Bouma | Lead developer LLBLGen Pro
TomDog
User
Posts: 618
Joined: 25-Oct-2005
# Posted on: 01-Jul-2014 06:39:58   

Otis wrote:

Yes, it doesn't do value change checking, it simply reflects whether it has set the value or not, to tell the user that a value was found in the relational model data.

Any chance you could make it to only notify on value change? A lot of noise otherwise.

Jeremy Thomas
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 01-Jul-2014 10:36:22   

TomDog wrote:

Otis wrote:

Yes, it doesn't do value change checking, it simply reflects whether it has set the value or not, to tell the user that a value was found in the relational model data.

Any chance you could make it to only notify on value change? A lot of noise otherwise.

Changed in v4.2 RTM.

Frans Bouma | Lead developer LLBLGen Pro