Sql updating identity column

The data in the table should look like so: If you’re looking to master your T-SQL Fu, I recommend this book.It provides a great reference for advanced T-SQL querying techniques.

The XPO architecture allow the identity column to be used only for a key field.

The persistent property always writes the value to the database if it isn't mapped to the auto-generated key column.

The persistent class can have only one key property. well, how have write a readonly prop to be read from DB.

You need either remove the Progressivo property from the persistent class, or use it as the key. I tried Non Persistent but the field is not included in SELECT statement generated by XPO engine. My impression is that XPO is a "DEAD MAN WALKING" No significant improvement in last Update Nothing intersting (comparing with the rest of the suite) in forecast basically XPO is just a sword that Dev Ex "have to mantain".thanks. I had not seen your trick so I 'll investigate on this By the way - Calculated field on db are readonly and shlould be fetched by XPO Why do not create an attribute [Calculated Field] or something similar ???

does XPO handles calculated fields (without triks or strange workarounds) ? XPO are great for many things ..they are "dead man walking" I think i''ll have to look around for a "living" ORMthank you! I had not seen your trick so I 'll investigate on this By the way - Calculated field on db are readonly and shlould be fetched by XPO Why do not create an attribute [Calculated Field] or something similar ???

Leave a Reply