mysqls | It is written in JavaScript , crud for mysql.You | Runtime Evironment library

This package appears to have problems with MySQL 8.

Try to use mysql_client, this one helped me.

https://pub.dev/packages/mysql_client

The solution to the above post seems to be to first update the MariaDB JDBC Java client to the current stable version. In the pom.xml for Maven:

I find the error, it comes from the routing rule of odata v8.

The construction of the relationship between endpoints and OData routing template is based on a set of rules, such rules are called OData Routing Convention. For example, “CustomersController” is an OData controller when the controller name “Customers” is an entity set in a given Edm model. “EntitySetName + Controller” is one of the OData controller name convention.

That means we need to make the controller name and EdmModel keep consistent. For example, here's my EdmModel setting in startup:

No, you must delimit the identifier if it has certain punctuation characters.

In MySQL, the default identifier delimiter is the back-tick.

If you enable the ANSI or ANSI_QUOTES SQL modes, you can use double-quotes as an identifier delimiter.

If you don't want to use delimiters, you must choose a different convention for prefixing your table names. You could use _ for example.

Read https://dev.mysql.com/doc/refman/8.0/en/identifiers.html for more details on the characters permitted in identifiers without delimiters.

First we have to caveat this that "transactions" are a function of a particular engine. InnoDB is the primary engine used by people so I'll focus on that.

Yes, certainly there can be multiple transactions, because if there wasn't you would never have deadlocks.

But the binlog doesn't include anything that wasn't committed:

Binary logging is done immediately after a statement or transaction completes but before any locks are released or any commit is done. This ensures that the log is logged in commit order.

So by necessity, the transaction log is inherently serialized.

MariaDB has some InnoDB documentation that includes this:

You can modify data on a maximum of 96 * 1023 concurrent transactions that generate undo records. Of the 128 rollback segments, InnoDB assigns 32 to non-redo logs for transactions that modify temporary tables and related objects, reducing the maximum number of concurrent data-modifying transactions to 96,000, from 128.000. The limit is 32,000 concurrent transactions when all data-modifying transactions also modify temporary tables.

The purpose of the log is to be able to recover from a catastrophic loss, by being able to replay completed statements and transactions. If recovery goes through the transaction log and a transaction is never committed, that transaction isn't in the transaction log.

Each DbContext can config their own entity

Let assume we have 10 entities for 3 DbContext, we can separate them out 2 entities for ADbContext, 5 for BDbContext and 3 for CDbContext. Manage the configuration like FK, between them wisely, otherwise, that would turn to be chaos. Here is how to doing this, using fluent API

Although I'm still not able to connect to the SQL Server on Azure, the problem of finding the right connection string format has been solved. I was able to connect to a local server using:

I guess this happens when you're using an ODBC driver which internally uses libmysqlclient. The thing is, libmysqlclient doesn't restart system calls interrupted by signals, and GHC runtime uses signals internally.

You can see how you can avoid this by looking at Database.HDBC.MySQL.withRTSSignalsBlocked. Simply put, this function blocks SIGALRM and SIGVTALRM which are used by GHC runtime while executing your code block. You may directly use this function, or you can just copy it if you don't want to depend on HDBC-mysql.

I think you should correct this: