workbench | Tooling around scala-js | Build Tool library

I came across the same issue trying to scaffold an existing MySQL database. It looks like the latest version of MySql.EntityFrameworkCore (6.0.0-preview3.1) still uses the EFCore 5.0 libraries and has not been updated to EFCore 6.0.

It also seems Microsoft.EntityFrameworkCore.Diagnostics was last implemented in EFCore 5 and removed in 6.

When I downgraded all the packages to the 5 version level, I was able to run the scaffold command without that error.

I had the same problem after upgrade to 8.0.27. Had no clue how to solve it.

I downgraded MySQL Workbench back to 8.0.19, and the 'No' and 'If Available' options came back.

Maybe they just want you to buy Navicat I guess.

First install this plugin from Visual Studio Code (witch you already did) :

Try to run command netstat -nltp. It shows active addresses and ports. Your nginx process should be run at 0.0.0.0:8000. 0.0.0.0 means the nginx process is available from anywhere.

If your nginx process is ran by any specific ip address, you should access it by that ip address, e.g http://192.168.4.2:8000.

You don't need to set secure-file-priv if you use LOAD DATA LOCAL INFILE. This allows the client to read the file content on the computer where the client runs, so you don't have to upload the file to the designated directory on the database server. This is useful if you don't have access to the database server.

But the LOCAL option is disabled by default. You have to enable it in both server and client with the local-infile option in my.cnf on the server, and also using in the MySQL client by using mysql --local-infile.

In addition, your user must be granted the FILE privilege to load files into a table. See https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html

Once it's working, LOAD DATA INFILE should be the fastest way to bulk-load data. I did a bunch of comparative speed tests for a presentation Load Data Fast!

You may also have some limiting factors with respect to MySQL Server configuration options, or even performance limitations with respect to the computer hardware.

I think the 5 hours for 30k records is way too long even on modest hardware.

I tested on a Macbook with builtin SSD storage. Even in my test designed to be as inefficient as possible (open connection, save one row using INSERT, disconnect), I still was able to insert 290 rows/second, or 10k rows in 34 seconds. The best result was using LOAD DATA INFILE, at a rate of close to 44k rows/second, loading 1 million rows in 22 seconds.

So something is severely underpowered on your database server, or else the Import Wizard is doing something so inefficient I cannot even imagine what it could be.

Consider the following steps:

1. Open MySQL workbench
2. right-click on the particular MySQL instance and select "Edit Connection"
3. Select the "SSL" tab under Connection Method
4. Select the drop-down for the "Use SSL" and choose "If Available" instead of "Required".
5. Click the "Test Connection" button at the lower right connection to make sure you can now connect without errors.

You need to downgrade to a lower workbench version here in order to see more options in the drop-down from step 4.

1 pod has unbound immediate PersistentVolumeClaims. - this error means the pod cannot bound to the PVC on the node where it has been scheduled to run on. This can happen when the PVC bounded to a PV that refers to a location that is not valid on the node that the pod is scheduled to run on. It will be helpful if you can post the complete output of kubectl get nodes -o wide, kubectl describe pvc triplestore-data-storage, kubectl describe pv triplestore-data-storage-dir to the question.

The mean time, PVC/PV is optional when using hostPath, can you try the following spec and see if the pod can come online:

I don't know if it may be the right approach for you, but what I did is downgrade my version of MySQL Workbench to 6.3 and uninstalled the previous version and it will then give you the "if available" option for SSL. As you are right, it is not the case for previous versions, however you do lose a few more modern features in the process.

https://downloads.mysql.com/archives/workbench/

Another solution as well is to connect to connect to the database in 6.3 and since the configuration saves are in same location, upgrade to 8.0 where it will still have the old configuration file and won't use SSL due to backwards compatibility.

The procedure receives a name as its argument and returns a server-side cursor with that name. On the client side, after calling the procedure you must declare a named cursor with the same name and use it to access the query results. You must do this before committing the connection, otherwise the server-side cursor will be destroyed.