Attempt to write a read-only database
Posted: Wed 01 Jul 2015 19:47
I don't know why but I have exception "Attempt to write a read-only database" by calling SubmitChanges()
by Devart.Data.Linq.LinqCommandExecutionException.CanThrowLinqCommandExecutionException(String message, Exception e)
by Devart.Data.Linq.DataProvider.b(String A_0, IEnumerable`1 A_1, IEnumerable`1 A_2, Boolean A_3)
by Devart.Data.Linq.DataProvider.a(String A_0, IEnumerable`1 A_1, IEnumerable`1 A_2, Boolean A_3)
by Devart.Data.Linq.Engine.SubmitCommandBuilder.a(IObjectEntry A_0)
by Devart.Data.Linq.Engine.b4.a(IObjectEntry[] A_0, ConflictMode A_1, a A_2)
by Devart.Data.Linq.Engine.b4.a(ConflictMode A_0)
by Devart.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode)
by Devart.Data.Linq.DataContext.SubmitChanges()
By previous tests all worked fine but in the table was auto incremented key and was no relation.
This time I need to create tree nodes, so I create first all nodes in memory and then store it to database.
What you could suggest me to test/to check why I receive this message? I enable the log but can't see there any error message.
by Devart.Data.Linq.LinqCommandExecutionException.CanThrowLinqCommandExecutionException(String message, Exception e)
by Devart.Data.Linq.DataProvider.b(String A_0, IEnumerable`1 A_1, IEnumerable`1 A_2, Boolean A_3)
by Devart.Data.Linq.DataProvider.a(String A_0, IEnumerable`1 A_1, IEnumerable`1 A_2, Boolean A_3)
by Devart.Data.Linq.Engine.SubmitCommandBuilder.a(IObjectEntry A_0)
by Devart.Data.Linq.Engine.b4.a(IObjectEntry[] A_0, ConflictMode A_1, a A_2)
by Devart.Data.Linq.Engine.b4.a(ConflictMode A_0)
by Devart.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode)
by Devart.Data.Linq.DataContext.SubmitChanges()
By previous tests all worked fine but in the table was auto incremented key and was no relation.
This time I need to create tree nodes, so I create first all nodes in memory and then store it to database.
What you could suggest me to test/to check why I receive this message? I enable the log but can't see there any error message.