Issue Details (XML | Word | Printable)

Key: DNET-769
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Jiri Cincura
Reporter: Jiri Cincura
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
.NET Data provider

Big models overrun the hex literal limit when inserting into __MigrationHistory

Created: 01/Jun/17 11:06 AM   Updated: 08/Oct/18 08:52 AM
Component/s: Entity Framework
Affects Version/s: 5.9.1.0
Fix Version/s: 6.4.0.0

Issue Links:
Duplicate
 


 Description  « Hide
Instead of one big insert, multiple smaller updates might be a way out.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Maxim Grishin added a comment - 24/Jul/18 07:53 PM - edited
Hello! As per Contributing file in your repository, I want to announce my intention to solve this one, because it`s kinda showstopper when using Firebird with Entity Framework.

I already have working prototype of migration, but I think it`s not perfect and requires some external help as I`m not that experienced when it comes to provider development.

I took an idea from description: instead of one big insert I'm splitting it into insert and subsequent updates (like UPDATE __MigrationHistory SET Model = Model || 'datachunk' WHERE MigrationId = 'id'). I'm doing it via modification of commandTree variable + creating new trees based on commandTree in FbMigrationSqlGenerator.cs > Generate(HistoryOperation) function and it works.

Jiri Cincura added a comment - 24/Jul/18 07:56 PM
Feel free to create PR at https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient and we can take it from there.