I'm trying to get logging to work (but I've not managed so far, I tried built in logging first, then log4net. I just want to see all sql-statements issued in the debug log.. I've followed the documentation, then some threads in the forum. At least I haven't any configuration-related exceptions anymore..)

However, under certain conditions (I don't know exactly when, it's related to configuration of logging somehow) I start to get a lot of exceptions thrown into the debug log (but not through the logging framework.) It's two exceptions:

Xtensive.Orm.Upgrade.Model.ValidationException and some AggregateException with the exception above.

It's allways about some index that's invalid, wrong columns are included. I've checked in the db and every index has "TypeId" added as an included column, independent of whether the key column is included or not in the index. Almost all tables have the TypeId-field, but it seems strange the the TypeId column is added to indexes where the Id column isn't

Dataobjects.net 4.5 MSSQL

asked Oct 18 '12 at 09:04

Onkelborg's gravatar image

Onkelborg
677712


One Answer:

Hello Onkelborg,

currently TypeId is included in secondary indexes as value column if storage supports that.

This is somewhat legacy behavior. We'll consider removing it in future versions of DO.

answered Oct 23 '12 at 09:56

Denis%20Krjuchkov's gravatar image

Denis Krjuchkov
179325

Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview

Subscription:

Once you sign in you will be able to subscribe for any updates here

Tags:

×573
×8
×2

Asked: Oct 18 '12 at 09:04

Seen: 3,385 times

Last updated: Oct 23 '12 at 09:56

powered by OSQA