You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a schema update coming to a database I'm tracking and I can't get OrcaMDF to read the new column (it always returns null). The new column is a nullable bit, exactly like an existing column.
TL;DR NoteTypeActive always reads correctly, NoteArchived will not.
Here's the schema for the table:
Here's a screenshot of some data:
Here's my code to read the field:
I'm using Boolean? to read the row value according to this document. I've also tried int?, bool?, and string without any success.
For context, I've used OrcaMDF to import millions of records and never had any issues. I'm at a loss to explain why the schema change would cause the data type to seemingly break. I'm running SQL Server 2012 on WS 2012.
The text was updated successfully, but these errors were encountered:
I realize this code/issue is a few years old, but after I hit another issue (#29) I decided to dig around a bit. There's definitely an issue with OrcaMDF reading tables on the first page.
I was able to "fix" it by truncating/re-inserting data in the problem table (from SQL, not OrcaMDF). This resets the page pointer which OrcaMDF then reads correctly. I also took the opportunity to change the data type for certain fields from bit to varchar which will read all values consistently.
I have a schema update coming to a database I'm tracking and I can't get OrcaMDF to read the new column (it always returns null). The new column is a nullable bit, exactly like an existing column.
TL;DR NoteTypeActive always reads correctly, NoteArchived will not.
Here's the schema for the table:
Here's a screenshot of some data:
Here's my code to read the field:
I'm using Boolean? to read the row value according to this document. I've also tried int?, bool?, and string without any success.
For context, I've used OrcaMDF to import millions of records and never had any issues. I'm at a loss to explain why the schema change would cause the data type to seemingly break. I'm running SQL Server 2012 on WS 2012.
The text was updated successfully, but these errors were encountered: