dotConnect for MySQL 9.0.0.0
Any ideas to fix this problem?
Search found 15 matches
- Wed 07 Sep 2022 22:21
- Forum: dotConnect for MySQL
- Topic: Arithmetic operation resulted in an overflow
- Replies: 1
- Views: 9850
- Fri 13 Nov 2020 12:55
- Forum: dotConnect for MySQL
- Topic: bufferAdapter is not a VsTextDocData
- Replies: 4
- Views: 24585
Re: bufferAdapter is not a VsTextDocData
Thanks for advice! Changing the Model, closing it, will prompt for saving changes – works too.
I’m looking forward to see VS 2019 16.8 and EF 5 support.
Best regards!
I’m looking forward to see VS 2019 16.8 and EF 5 support.
Best regards!
- Thu 12 Nov 2020 22:01
- Forum: dotConnect for MySQL
- Topic: bufferAdapter is not a VsTextDocData
- Replies: 4
- Views: 24585
bufferAdapter is not a VsTextDocData
Any help on this?
I have a new project using .NET 5. I’m trying to use EF 6 and Devart dotconnect.
I have a new project using .NET 5. I’m trying to use EF 6 and Devart dotconnect.
- Wed 11 Nov 2020 07:59
- Forum: dotConnect for MySQL
- Topic: EF Core 5 Support
- Replies: 2
- Views: 3297
EF Core 5 Support
When will EF Core 5 support will arrive?
- Wed 30 Sep 2020 07:18
- Forum: dbForge for MySQL
- Topic: Bug: DEFAULT (CURRENT_TIMESTAMP) in Table Columns with Storage Engine “MEMORY”
- Replies: 1
- Views: 3336
Bug: DEFAULT (CURRENT_TIMESTAMP) in Table Columns with Storage Engine “MEMORY”
Trying
throws error “'Specified storage engine' is not supported for default value expressions. SQL1.sql 1 1”. If one omits “DEFAULT (CURRENT_TIMESTAMP)”, it’s working. But whole SQL statement it’s working on phpmyadmin for example.
dbForge Studio 9.0.391
MySQL 8.0.21
Best regards!
Code: Select all
CREATE TABLE access_protection_test (
ip_address VARBINARY(16) NOT NULL,
last_access_time TIMESTAMP NOT NULL DEFAULT (CURRENT_TIMESTAMP) ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (ip_address)
)
ENGINE = MEMORY,
CHARACTER SET utf8mb4,
COLLATE utf8mb4_0900_ai_ci;
dbForge Studio 9.0.391
MySQL 8.0.21
Best regards!
- Fri 28 Aug 2020 09:19
- Forum: dotConnect for MySQL
- Topic: Wrong Entity Framework provider type after upgrading to 8.17.1696?
- Replies: 2
- Views: 5026
Re: Wrong Entity Framework provider type after upgrading to 8.17.1696?
It turns out that Visual Studio(?) did not rebuilded all *.config. I had to clear /bin and /obj. After build the correct configs are created by Visual Studio.
- Thu 27 Aug 2020 22:07
- Forum: dotConnect for MySQL
- Topic: Wrong Entity Framework provider type after upgrading to 8.17.1696?
- Replies: 2
- Views: 5026
Wrong Entity Framework provider type after upgrading to 8.17.1696?
After upgrading (with wizard) to dotConnect for MySQL 8.17.1696 I get the following Exception if I run the application (WPF, .NET Framework 4.8):
The Entity Framework provider type 'Devart.Data.MySql.Entity.MySqlEntityProviderServices, Devart.Data.MySql.Entity.EF6, Version=8.17.1666.0, Culture=neutral, PublicKeyToken=09af7300eec23701' registered in the application config file for the ADO.NET provider with invariant name 'Devart.Data.MySql' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
App.config contians:
References:
Best regards!
The Entity Framework provider type 'Devart.Data.MySql.Entity.MySqlEntityProviderServices, Devart.Data.MySql.Entity.EF6, Version=8.17.1666.0, Culture=neutral, PublicKeyToken=09af7300eec23701' registered in the application config file for the ADO.NET provider with invariant name 'Devart.Data.MySql' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
App.config contians:
Code: Select all
<entityFramework>
<providers>
<provider invariantName="Devart.Data.MySql"
type="Devart.Data.MySql.Entity.MySqlEntityProviderServices, Devart.Data.MySql.Entity.EF6, Version=8.17.1696.0, Culture=neutral, PublicKeyToken=09af7300eec23701" />
</providers>
</entityFramework>
- C:\Program Files (x86)\Common Files\Devart\dotConnect\NET2\Devart.Data.dll
- C:\Program Files (x86)\Common Files\Devart\dotConnect\NET2\Devart.Data.MySql.dll
- C:\Program Files (x86)\Devart\dotConnect\MySQL\Entity\EF6\Devart.Data.MySql.Entity.EF6.dll
Best regards!
- Mon 18 May 2020 13:12
- Forum: dotConnect for MySQL
- Topic: Entry state modified even if no property was modified (DbUpdateConcurrencyException)
- Replies: 4
- Views: 3767
- Wed 06 May 2020 11:59
- Forum: dotConnect for MySQL
- Topic: Entry state modified even if no property was modified (DbUpdateConcurrencyException)
- Replies: 4
- Views: 3767
Re: Entry state modified even if no property was modified (DbUpdateConcurrencyException)
Thank you. That’s strange …
If I set FoundRows = true in a MySqlConnectionStringBuilder instance, I don’t get the exception. Is setting FoundRows the right way / best practice?
If I set FoundRows = true in a MySqlConnectionStringBuilder instance, I don’t get the exception. Is setting FoundRows the right way / best practice?
- Thu 30 Apr 2020 12:21
- Forum: dbForge for MySQL
- Topic: dbForge MySQL 2020 Enhancement – option to disable animations
- Replies: 2
- Views: 1435
Re: dbForge MySQL 2020 Enhancement – option to disable animations
Cool! Thank you!
- Tue 28 Apr 2020 17:27
- Forum: dbForge for MySQL
- Topic: dbForge MySQL 2019 v8.2.23 not compatible with MySQL 8.0.20
- Replies: 4
- Views: 4373
Re: dbForge MySQL 2019 v8.2.23 not compatible with MySQL 8.0.20
Okay, thank you! :-)
- Tue 28 Apr 2020 11:12
- Forum: dbForge for MySQL
- Topic: dbForge MySQL 2020 Enhancement – option to disable animations
- Replies: 2
- Views: 1435
dbForge MySQL 2020 Enhancement – option to disable animations
For dbForge MySQL 2020 please add an option to disable animations. Namely the menu animations (fade-in) are annoying (at least for me).
- Tue 28 Apr 2020 10:24
- Forum: dbForge for MySQL
- Topic: dbForge MySQL 2019 v8.2.23 not compatible with MySQL 8.0.20
- Replies: 4
- Views: 4373
Re: dbForge MySQL 2019 v8.2.23 not compatible with MySQL 8.0.20
I’m unsure about the BETA. In the download section there is the note “For demo purposes only. Do not use for critical data”. But, I use it for critical/production data … I think, there should be a fix/release for the dbForge MySQL 2019 branch.
Edit: dbForge MySQL 2020 BETA works for MySQL 8.0.20.
Edit: dbForge MySQL 2020 BETA works for MySQL 8.0.20.
- Tue 28 Apr 2020 08:11
- Forum: dbForge for MySQL
- Topic: dbForge MySQL 2019 v8.2.23 not compatible with MySQL 8.0.20
- Replies: 4
- Views: 4373
dbForge MySQL 2019 v8.2.23 not compatible with MySQL 8.0.20
dbForge MySQL 2019 v8.2.23 ist not compatible with MySQL 8.0.20. After trying to connect, I just get the message: “This server version 8.0.20 is not currently supported.”
- Mon 27 Apr 2020 12:58
- Forum: dotConnect for MySQL
- Topic: Entry state modified even if no property was modified (DbUpdateConcurrencyException)
- Replies: 4
- Views: 3767
Entry state modified even if no property was modified (DbUpdateConcurrencyException)
If I set a property of an entity Album, let’s say Album.Name = "Greatest Hits", but Album.Name == "Greatest Hits" was true before, DbContext.Entry<Album>(Album).State is set to EntityState.Modified. This seems to be wrong, because there is no change.
If I call DbContext.SaveChanges() later, I get an odd DbUpdateConcurrencyException. If you catch this exception, you can compare database values and local values (see https://docs.microsoft.com/en-us/ef/ef6 ... oncurrency). But these values do not differ!
This seems to be a bug. I can try to create a minimal working example if needed.
If I call DbContext.SaveChanges() later, I get an odd DbUpdateConcurrencyException. If you catch this exception, you can compare database values and local values (see https://docs.microsoft.com/en-us/ef/ef6 ... oncurrency). But these values do not differ!
This seems to be a bug. I can try to create a minimal working example if needed.