MySQL Forums

Help with EXPLAIN (3 replies)

John Noble — Fri, 18 Sep 2026 13:36:22 +0000

Hi there,

I have a large complicated stored procedure that appears to be running quite slow. When I use the EXPLAIN keyword, I get the following feedback...

id,select_type,table,type,possible_keys,key,key_len,ref,rows,Extra
1,PRIMARY,,ALL,NULL,NULL,NULL,NULL,4443,"Using filesort"
2,DERIVED,salesledger,range,"doctype,invoiceDate,paidinfulldate",paidinfulldate,4,NULL,4461,"Using where; Using temporary; Using filesort"
2,DERIVED,receipts,ref,invNum,invNum,4,sst.salesledger.invNum,1,
2,DERIVED,customers,ref,customerID,customerID,9,sst.salesledger.customerID,1,
2,DERIVED,groups,ALL,NULL,NULL,NULL,NULL,19,
2,DERIVED,users,ref,userID,userID,5,sst.salesledger.CCmanagerID,1,
2,DERIVED,countries,ref,countryID,countryID,4,sst.salesledger.countryID,1,
3,UNION,salesledger,range,"doctype,invoiceDate,paidinfulldate",paidinfulldate,4,NULL,4461,"Using where; Using temporary; Using filesort"
3,UNION,receipts,ref,paymentNo,paymentNo,4,sst.salesledger.paymentNo,1,
3,UNION,customers,ref,customerID,customerID,9,sst.salesledger.customerID,1,
3,UNION,groups,ALL,NULL,NULL,NULL,NULL,19,
3,UNION,users,ref,userID,userID,5,sst.salesledger.CCmanagerID,1,
3,UNION,countries,ref,countryID,countryID,4,sst.salesledger.countryID,1,
4,UNION,salesledger,ref,"invNum,invoiceDate,paidinfulldate",invNum,4,,1914,"Using where; Using temporary; Using filesort"
4,UNION,customers,ref,customerID,customerID,9,sst.salesledger.customerID,1,
4,UNION,groups,ALL,NULL,NULL,NULL,NULL,19,
4,UNION,users,ref,userID,userID,5,sst.salesledger.CCmanagerID,1,
4,UNION,countries,ref,countryID,countryID,4,sst.salesledger.countryID,1,
4,UNION,receipts,ALL,receiptDate,NULL,NULL,NULL,571339,"Using where; Using join buffer"
NULL,"UNION RESULT","",ALL,NULL,NULL,NULL,NULL,NULL,

Sorry, but I cannot see how to format the results.

The last entry shows rows as 571339. The posibble_keys is showing as receiptDate. However, there is already an index on Receipts.receiptDate but the key column is showing as null ??

Can anyone advise ?

Thanks,

John

MySQL Workbench 26.7 Connect Options for Local Infile (no replies)

Bryan Simmons — Wed, 16 Sep 2026 20:06:48 +0000

In a previous version of Workbench there was an option of OPT_LOCAL_INFILE=1 that could be added under advanced connection options. This appears to have changed with version 26.7 but I am unable to find details regarding location and syntax to apply this option in the later version.

For 26.7 there is an area under Edit Connection... -> Advanced -> Other Connection Options but the OPT_LOCAL_INFILE option is not recognized.

Is there documentation somewhere that explains this for 26.7 or does anyone known how to add this option (or equivalent)?

MySql WorkBench 26.7 Data Modeling (no replies)

Olman Núñez Peralta — Tue, 15 Sep 2026 15:42:10 +0000

Hi, in the new Workbench version (26.7) I couldn't find the option to create a data model. Is that correct? Will it be available in future releases?

Designing a scalable MySQL database for a healthcare website (no replies)

Jeevandan Health — Tue, 15 Sep 2026 10:23:16 +0000

Designing a scalable MySQL database for a healthcare website

Hello everyone,

I'm working on the database architecture for a healthcare website and would like to get some advice from experienced MySQL users.

The website needs to manage different types of structured information, such as departments, doctors, services, appointments, and general website content. I'm considering MySQL for the database layer and want to make sure the schema remains efficient as the amount of data grows.

A few things I'm particularly interested in:

How should related entities such as departments, doctors, and services be structured?
What indexing strategy would you recommend for frequently searched records?
Are there any common database-design mistakes I should avoid when building a healthcare-related website?
What are the recommended approaches for maintaining database performance as the number of records increases?
Would you recommend any particular backup and recovery strategy for this type of application?

I'd appreciate advice from anyone who has worked with MySQL databases for content-heavy or service-based websites.

Thanks in advance.

How to do export/import in MySQL Workbench 26.7.0 (no replies)

Andrii Perun — Mon, 14 Sep 2026 22:12:02 +0000

I've successfully installed MySQL Workbench 26.7.0 on Ubuntu 26. But I can't see the Server view and consequently can't find an Export/Import button there.

Any Impact of Oracle Restructuring on MySQL? (no replies)

Raj Mane — Sat, 12 Sep 2026 11:33:30 +0000

I’m a little concerned about the possible impact of Oracle’s restructuring on MySQL. If the restructuring results in fewer developers and support engineers working on MySQL, it could affect bug fixes, new releases, and the level of technical support available to users.

For businesses that have relied on MySQL for many years, moving to another database is not an easy decision. It would probably be better to monitor the situation closely and start evaluating alternatives rather than making an immediate switch.

Hopefully, the MySQL community and other companies involved in the ecosystem will continue supporting development and keeping the project moving forward.

Workbench update to 26.7.0 (1 reply)

Christian Marquardt — Fri, 11 Sep 2026 05:18:06 +0000

I update from 8.0.47 to 26.7.0
The installation was successful. The existing connections were successfully imported. Unfortunately, none of the connections are establishing a link to the database.
It is also not possible to test the connection.
There is no response; the spinning circle icon just keeps turning indefinitely.
Workbench System: Windows 11
Target database: MariaDB 10.11.14
Reinstalled version 8.0.47; it's running without problems.

Starting a Discussion About Database Migration (1 reply)

ortega blanks — Thu, 17 Sep 2026 13:44:13 +0000

Hello everyone,

I'm new to this forum and would like to start a discussion about database migration.

I'm interested in learning more about migrating databases to MySQL, the common challenges people face, and the best practices for a smooth migration.

I look forward to hearing about your experiences and learning from the community.

Thank you!

Upgrade Problems (2 replies)

Miguel Espinosa — Wed, 09 Sep 2026 14:24:33 +0000

I am having issues upgrading mysql database. It is giving me errors that the database is unusable any help would be greatly appreciated.

Discrepancy in Compatibility statement with MySQL and Connector/J 26.7 (2 replies)

Swann Puig — Sun, 30 Aug 2026 20:26:50 +0000

Hello,

I noticed what appears to be a discrepancy in the documentation regarding the minimum MySQL Server version supported by Connector/J 26.7.

In this page : https://dev.mysql.com/doc/connector-j/en/connector-j-versions.html
It is written "MySQL Server versions: Connector/J 26.7 supports MySQL 8.0 and up. "

But in the release notes in this page : https://dev.mysql.com/doc/relnotes/connector-j/en/news-26-7-0.html
It is written "This release can be used against MySQL Server version 8.4 and later."

My question is what is the correct minimal MySQL Server version officially supported by the new Connector/J 26.7 ?

Thank you for your help.

Best regards,

Announcing August 2026 Releases featuring MySQL Server, MySQL NDB Cluster, Shell and Connector/ODBC (no replies)

Balasubramanian Kandasamy — Tue, 25 Aug 2026 07:01:59 +0000


Dear MySQL users,

We are pleased to announce the release of the following products:

    * MySQL Server 26.7.1, 9.7.3 and 8.4.12 (Docker only)
    * MySQL Shell 26.7.1
    * Connector/ODBC 26.7.1
    * MySQL NDB Cluster 26.7.1, 9.7.3, 8.4.12 and 8.0.49 (Docker only)

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

https://dev.mysql.com/downloads/

Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors as they support both MySQL Server 8.4
and 9.7 too.

Enterprise binaries for these new releases are available on My Oracle
Support:

https://support.oracle.com

Choose the "Patches & Updates" tab, and then choose the "Product or
Family (Advanced Search)" side tab in the "Patch Search" portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

https://edelivery.oracle.com/

Developers can download MySQL Enterprise Edition from

https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html

Innovation releases are supported until the next innovation release, and
are recommended for production use. The 8.4 and 9.7 series
will focus on security and bug fixes only. Please refer to the following
for more information:

https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html

Changes since the previous releases can be viewed online:

https://dev.mysql.com/doc/#current-release-notes

On Behalf of the MySQL Engineering Team,
Balasubramanian Kandasamy

How to Troubleshoot Slow MySQL Queries Using EXPLAIN and Indexes (1 reply)

alex Tan — Tue, 01 Sep 2026 04:21:20 +0000

Slow database queries can affect the performance of an entire application. When a MySQL database becomes slower as the amount of data increases, checking how queries are executed is a good place to start.

Use EXPLAIN to Check the Query

MySQL provides the `EXPLAIN` statement to show how it plans to execute a query.

For example:

`EXPLAIN SELECT * FROM orders WHERE customer_id = 100;`

The result can help identify whether MySQL is using an index or scanning a large number of rows.

Check Whether the Correct Index Exists

Indexes can improve the speed of queries that frequently search, filter, or join records using particular columns.

For example, if `customer_id` is frequently used in a WHERE condition, creating an appropriate index may improve performance.

However, adding indexes to every column is not a good solution. Too many indexes can consume additional storage and can also affect the performance of INSERT, UPDATE, and DELETE operations.

Avoid Retrieving Unnecessary Data

Using `SELECT *` retrieves every column even when only a few are required.

Instead of:

`SELECT * FROM customers;`

you can retrieve only the required columns:

`SELECT customer_id, customer_name FROM customers;`

This can reduce the amount of unnecessary data being processed and transferred.

Review JOIN Conditions

Queries involving several tables may become slow when JOIN conditions are inefficient or when the columns involved are not indexed appropriately.

Using `EXPLAIN` on these queries can help determine how MySQL accesses each table.

Monitor Queries as the Database Grows

A query that performs well with a small database may become much slower when the tables contain thousands or millions of records. Regularly reviewing important queries and their execution plans can help identify performance problems before they become serious.

Conclusion

When troubleshooting slow MySQL queries, checking the execution plan with EXPLAIN, reviewing indexes, limiting unnecessary data retrieval, and checking JOIN conditions are useful starting points.

What methods do you normally use to identify and improve slow queries in MySQL?

The future of the timestamp data type (1 reply)

Lenny Andersen — Mon, 17 Aug 2026 20:30:13 +0000

Hi

I am trying to find a sustainable approach to using the "timestamp" data type.
The functions that use the timestamp type generally seem to support 64-bit values, but the actual value for the timestamp type is stored as a 32-bit value and therefore does not support timestamps after 2038-01-19 03:14:07 UTC.
And while 2038 may sound like the distant future, we are now closer to 2038 than "the year of the Ice Bucket Challenge" in 2014, so I feel it is about time to address this issue.

My problem is: I can find several posts on various forums about how to work around this issue, but I cannot find any official documentation from MySQL about what the plan is for this data type. Do they intend to upgrade the type to support 64-bit? Do they intend to deprecate the type? Or do they simply intend to mention it in passing in some release note 10 years from now?
(if anyone can point me to something I have overlooked, I would be very interested).

I fully understand that there are several ways to solve the problem (personally, I just use bigint and convert with unix_timestamp() and from_unixtime()), but I am missing an official statement on how MySQL intends to handle this issue.

Anyone who can help me out?

Linking 2 cells in a table (no replies)

Eric Crastes — Thu, 13 Aug 2026 11:07:46 +0000

Hi

I searched through the web and couldn't find an answer, but may be it's too difficult to explain what I'm looking for to a search engine

I have a table, already existing with thousand of rows in it
I need to add a new column with a value linked permanently to the value of another column, but not the same row

like
row 1 : status = OK
row 2 : statusfrom1 = row1(status)

not just when creating the row2 but dynamically, if I change row1(status) then row2(statusfrom1) will be automatically updated

kind of "softlink" for files under Unix , if you see what I mean

Is it possible ?

I know that the best way to achieve that will be to have an extra table but this may imply to me to rewrite a lot of stuff behind and also the table is full, I would like to avoid to update all rows

Thanks
Ericc

MySQL syntax error - don't get it! (3 replies)

Gregary Boyles — Thu, 10 Sep 2026 20:58:46 +0000

SELECT * FROM millhouse_db.sponsors WHERE type='funding' ORDER BY rank ASC;

Apparently there is a syntax error near ASC.

Don't get it!

What is the error?

replication from 8.0 to 8.4 error (1 reply)

David James — Tue, 25 Aug 2026 11:08:21 +0000

Hello
We have a newly installed 8.4.10-10 mysql database running on Rocky Linux 8.10.

Trying to configure it as the replica for a 8.0.37-29 mysql database.

The error upon checking is

Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the source's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the replica's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, the server was unable to fetch a keyring key required to open an encrypted relay log file, or a bug in the source's or replica's MySQL code. If you want to check the source's binary log or replica's relay log, you will be able to know their names by issuing 'SHOW REPLICA STATUS' on this replica.

We thought this might have been an OS issue as we first attempted this on Ubuntu. But now having movied to Rocky we are getting the exact same error.

Has anyone seen this before? From what I understand this is supported (8.0 to 8.4) but for life of me I cant get past this error!

Thanks.

This CMD window bothers me. (2 replies)

Joachim von Kienitz — Wed, 26 Aug 2026 11:12:38 +0000

Whenever MySQL starts, a CMD window appears with the line "Apache 2 is starting ..." at the bottom.
How can I minimize this window?

Announcing July 2026 Releases featuring MySQL Server 26.7.0, 9.7.2 and 8.4.11 (no replies)

Balasubramanian Kandasamy — Sat, 01 Aug 2026 10:40:10 +0000


Dear MySQL users,

We are pleased to announce the release of the following products:

    * MySQL Server 26.7.0, 9.7.2, and 8.4.11
    * MySQL Shell, Router, Operator, NDB Operator and Connectors 26.7.0
    * MySQL NDB Cluster 26.7.0, 9.7.2, 8.4.11, and 8.0.48

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

https://dev.mysql.com/downloads/

Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors as they support both MySQL Server 9.7 and
8.4 LTS too.

As of this release, MySQL Router, MySQL Shell, MySQL Operator, and NDB
Operator adopt a single-version release model. The 8.4 and 9.7 release
series for these products have been discontinued, and only the 26.7
release series is available. The latest version of these products 
remains compatible with all supported MySQL Server 8.4, 9.7, and 26.7.

Windows packages are available via MSI or .ZIP (no-install) packages.
The MySQL Configurator tool, bundled with the MySQL Server Windows
packages, provides a user interface for creating and modifying MySQL
Server configurations on  Microsoft Windows platforms.

Enterprise binaries for these new releases are available on My Oracle
Support:

https://support.oracle.com

Click on the “Patches” tab, and then choose the “Product” and "Release"
filters in the “Patch Search” portlet

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

https://edelivery.oracle.com/

Developers can download MySQL Enterprise Edition from

https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html

Innovation releases are supported until the next innovation release, and
are recommended for production use. The 8.4 and 9.7 series will focus on
security and bug fixes only. Please refer to the following for more
information:

https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html

Changes since the previous releases can be viewed online:

https://dev.mysql.com/doc/#current-release-notes


On Behalf of the MySQL Engineering Team,
Balasubramanian Kandasamy

Can I purge binlog files after migration ? (no replies)

Vito Cavallo — Fri, 31 Jul 2026 14:45:13 +0000

Hello,
I performed a mysqldump and restore of a 5.7 database to a test server space.
It created approx 445 binlog.000xxx files that are 1 GB each.

Same thing happening via MySQL workbench restore.
Is this normal and can I purge them after migration ?

When I perform the command on the original server, SHOW BINARY LOGS; I receive "Error Code: 1381. You are not using binary logging"

I do not have any binary logging setup in my my.cnf.

I read a few with mysqlbinlog and it seems dates are recent.

Thank you.

Can't update expired password in Mysql Workbench (2 replies)

Don Lewis — Tue, 15 Sep 2026 13:11:09 +0000

Updating expired password in mysql workbench

Can't update password, get error every time

Password expired Please pick a new password
When enter old password and new passwords get error:
You have and error in your SQL syntax near PASSWORD('') at line 1 code 1064

mysqlworkbench version 8.0.47 community
mysql version 8.4.8-8

Assistance with MySql application and Sql server (1 reply)

EJIKE NWANKWO — Fri, 18 Sep 2026 13:32:04 +0000

Good morning all,
Please, can anybody assist me in downloading the farmers market database in SQL.
I downloaded the Mysql application but could not go further wiith the farmers data base

MySQL Community Governance Model (no replies)

Balasubramanian Kandasamy — Thu, 25 Jun 2026 18:24:00 +0000

Dear MySQL Community,

As part of our ongoing commitment to fostering a more open,
collaborative, and transparent development process, we are pleased to
share the MySQL Community Governance Model.

This builds on the vision outlined in our recent blog post, The Next
Phase of MySQL Community Engagement: Accelerating Participation and
Collaboration:
https://blogs.oracle.com/mysql/the-next-phase-of-mysql-community-engagement-accelerating-participation-and-collaboration

The governance model establishes a framework for how the MySQL community
can participate in the project's technical evolution while preserving
the quality, stability, security, and compatibility that users and
organizations rely on.

This covers several key areas, including:

* A governance structure defining the roles and responsibilities of Contributors, Committers, Project Leads,
Core Project Leads, and the Steering Committee.
* A transparent, merit-based path for increased community participation and leadership.
* Technical review, decision-making, and contribution processes designed to ensure high-quality development.
* A phased approach toward greater openness and earlier community engagement in the development lifecycle.
* Governance practices for proposals, releases, issue management, security coordination, and conflict resolution.

The governance model is intended to evolve alongside the MySQL project
and its community. As our development practices and collaboration
continue to mature, we expect this framework to be refined based on
practical experience and community input.

We invite members of the MySQL community—including developers, users,
customers, partners, and open source contributors—to share their
feedback. In particular, we welcome comments on:

* The overall governance structure and participation model.
* The clarity of roles and responsibilities.
* The technical review and decision-making processes.
* Opportunities to improve transparency, collaboration, and community participation.

Your participation will help shape the future of MySQL's community
governance and ensure that the model reflects the needs and perspectives
of our diverse ecosystem.

Please join us for our next public discussion on July 15 at 7 am Pacific
Time. https://oracle.zoom.us/webinar/register/WN_khcji3biT2m7myg6hDId4w

Announcing June 2026 Releases featuring MySQL Server 9.7.1 and 8.4.10 (no replies)

Balasubramanian Kandasamy — Wed, 24 Jun 2026 12:41:00 +0000


Dear MySQL users,

We are pleased to announce the release of the following products:

    * MySQL Server 9.7.1 and 8.4.10
    * MySQL Shell, Router 9.7.1 and 8.4.10
    * MySQL Shell for VS Code 2026.05+9.7.0
    * MySQL NDB Cluster 9.7.1, 8.4.10 and 8.0.47

These releases are recommended for use on production systems and are
available in source and binary form for a number of platforms from our
MySQL Community download pages at:

https://dev.mysql.com/downloads/

Regardless of server version, always use the latest version of MySQL
Clients, Tools, and Connectors as they support both MySQL Server 8.4
and 9.7 too.

Enterprise binaries for these new releases are available on My Oracle
Support:

https://support.oracle.com

Choose the "Patches & Updates" tab, and then choose the "Product or
Family (Advanced Search)" side tab in the "Patch Search" portlet.

MySQL Enterprise binaries are also available on the Oracle Software
Delivery Cloud:

https://edelivery.oracle.com/

Developers can download MySQL Enterprise Edition from

https://www.oracle.com/mysql/technologies/mysql-enterprise-edition-downloads.html

Innovation releases are supported until the next innovation release, and
are recommended for production use. The 8.0, 8.4 and 9.7 series
will focus on security and bug fixes only. Please refer to the following
for more information:

https://dev.mysql.com/doc/refman/8.4/en/mysql-releases.html

Changes since the previous releases can be viewed online:

https://dev.mysql.com/doc/#current-release-notes

On Behalf of the MySQL Engineering Team,
Balasubramanian Kandasamy

What could cause .frm and .ibd mismatches across multiple tables? (2 replies)

maria b — Tue, 01 Sep 2026 13:31:21 +0000

Hello,

We recently encountered a very strange issue on a production MySQL/MariaDB server and I'm trying to understand what could have caused it.

We have a Laravel application. A few days ago we noticed that a table seemed to be missing. After selecting the database and running:

SHOW TABLES;

the table did not appear in the list.

However, we were still able to query it:

SELECT * FROM table_name;

and the query returned data successfully.

At that point we executed:

FLUSH TABLES;

After that, the SELECT statement stopped working.

We then inspected the database directory under:

/var/lib/mysql//

and discovered that this was not limited to a single table. A significant number of tables were in an inconsistent state:

* Some tables had both .frm and .ibd files.
* Some tables had only a .frm file.
* Some tables had only a .ibd file.

We attempted to restore the database from the previous day's backup, but to our surprise the same inconsistencies were already present there. My understanding is that mysqldump only exports tables that MySQL can see through its metadata, so tables that only had orphaned .ibd files would not have been included in the dump ¿?

Eventually we had to restore from a backup that was about 5 days old, where all expected tables and files were present and consistent.

My questions are:

1. What kinds of events can lead to this type of inconsistency between .frm and .ibd files? - (the disk storage wasn't full)

2. Do people typically implement checks in production to detect mismatches between .frm and .ibd files before backups are taken? Cuz we always assumed that a successful mysqldump was enough

Additional environment information:

Operating System: Debian 12

Database Server: MariaDB 10.11.14

Version output:
mariadb Ver 15.1 Distrib 10.11.14-MariaDB, for debian-linux-gnu (x86_64)

innodb_file_per_table is enabled:
SHOW VARIABLES LIKE 'innodb_file_per_table';

Result:
+-----------------------+-------+
| Variable_name | Value |
+-----------------------+-------+
| innodb_file_per_table | ON |
+-----------------------+-------+

Version details:
SHOW VARIABLES LIKE 'version%';

Result:

version = 10.11.14-MariaDB-0+deb12u2-log
version_comment = Debian 12
version_compile_machine = x86_64
version_compile_os = debian-linux-gnu

Any ideas or similar experiences would be greatly appreciated!!

Problem with creating a connection to a remote database on local network (no replies)

Gregary Boyles — Wed, 03 Jun 2026 13:44:29 +0000

I am getting an access denied error if regardless of whether I use root or gregaryb as my username.

How do I fix this?

Best MySQL schema for storing image processing jobs? (3 replies)

Moez Cherif — Tue, 25 Aug 2026 07:25:27 +0000

I'm building an application that processes user-uploaded images through an API.

Each image goes through multiple stages:
- Uploaded
- Queued
- Processed
- Completed

I'm curious how others design MySQL tables for this type of workflow.

Do you use separate tables for jobs and results, or a single table with status columns?

APT Repository not working on Ubuntu 26.04 (10 replies)

Jos Vlaar — Wed, 16 Sep 2026 06:09:24 +0000

I am trying to install the official MySQL repository on my Ubuntu 26.04 VirtualBox virtual machine. I ran the following commands:

wget https://dev.mysql.com/get/mysql-apt-config_0.8.39-1_all.deb
sudo dpkg -i mysql-apt-config_0.8.39-1_all.deb
rm mysql-apt-config_0.8.39-1_all.deb

When running these commands the first time, I got a message saying my distribution (resolute) is not supported by MySQL. I aborted the installer there.

When running these commands again later, I don't get this error anymore. But when running sudo apt update, I get the following output:

Ign:7 http://repo.mysql.com/apt/ubuntu resolute InRelease
Err:8 http://repo.mysql.com/apt/ubuntu resolute Release
404 Not Found [IP: 2a02:26f0:fe00:2ab::1d68 80]
Error: The repository 'http://repo.mysql.com/apt/ubuntu resolute Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.

How come I aborted the installer, but the repository was still added?
How come Ubuntu 26.04 is still not supported? It was released more than a month ago...
Is there any other way to get this to work?

storing and reading blob (no replies)

charles candy — Thu, 28 May 2026 11:21:29 +0000

Hi,
I store file in db in blob but overtime become 30GB. even though i restrict file size less than 1mb.

the db become slow that simple "select * from img" very slow.

i thinking simplest change is export all blob out using INTO DUMPFILE and read it using LOAD_FILE .

my question . is this good solution ? or worse than store in db .

ODBC Connector almost always alters it's name and path (no replies)

Horst Wieland — Fri, 15 May 2026 11:04:23 +0000

The ODBC Connector sometimes gets updated from administrators, when a new version is available. That's commendable. Always the newest Connector is recommended.

But since the new versioning scheme is active, the "newest" connector always alters it's installation path and Name including the first decimal as from 9.6 to 9.7.
In order to get a working environment, also all existing ODBC data sources require to be modified to use the new version as well.

When updating only to minor versions as 8.0.x, the installation path and Name (in "ODBC Data Sources") is kept.

Would there be a strategy to be able to update the connector without constantly touching the data source definitions?

Such drivers from Microsoft e.g. mostly retain their general names and access, even with major versions. Updating a driver does not need to modify the data sources then.

Connector/Windows (1 reply)

Emmanuel BILLOT — Wed, 16 Sep 2026 13:45:47 +0000

Hi,

Is there anyway to query a MySQL server from en Windows client in PowerShell WITHOUT installing any software/driver on it ?

We wander if it is possible to execute a light PowerShell script from any client connected to the network, from a share, making some select and insert, but with no MySQL connector install.

Using "[void][system.reflection.Assembly]::LoadFrom" we got errors, and no cmdlets recognized.

One "dirty" way should use a mysql.exe from a share, but results are unusable.

Could it be possible to "load" MySQL libs or cmd "on the fly" with no install on the computer executing the powershell script ?

Regards,