I'm using the SelfServicing model with LLBLGen Pro v2., SQL Server 2000 database

I have a table called "Members" in my database. It has a computed column called "LoweredUserName".

In the "Mapped entity fields" property grid in the LLBLGen main window, the following properties are displayed:

"Is readonly = True", "Is computed = True".

I would have expected the generated Entity code to have a readonly field for "LoweredUserName", but it's not (it's read/write)

The other thing is that the "Is nullable" property in the grid is set to "True" - would this be the cause?

Tim

Did you succeed in setting a value to it? I think the readonly check is done when you set the value.

Yes, I could set a value - the property is read/write, even though in the database it is a computed column.

Wouldn't you expect the property to be read only?

Meteor wrote:

Yes, I could set a value - the property is read/write, even though in the database it is a computed column.

Wouldn't you expect the property to be read only?

http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=4238

Thanks for the quick responses.

Still, for a non-PK readonly database field, I'd have expected that there was no setter for that property in the generated entity.

To me that would be more intuitive than throwing a runtime error.

Meteor wrote:

Thanks for the quick responses.

Still, for a non-PK readonly database field, I'd have expected that there was no setter for that property in the generated entity.

To me that would be more intuitive than throwing a runtime error.

That's also what we thought so we changed it in v2.5 (now in beta, free upgrade for v2.0 users) Readonly fields dont have a setter anymore, except PK fields.