no HotDB database selected

lin.chq's profile image lin.chq posted 3 years ago in Creating a connection Permalink

When I connect to a MySQL database,distributed deployment, It report this error as shown in the figure;

SQL错误(1046):No HotDB Database selected;

HotDB is a distributed transaction database product

Please help to check it

1 attachment(s):
  • -_20210424153019
ansgar's profile image ansgar posted 3 years ago Permalink

You could connect to some working session first, so you can look up the failing query in the log panel when you connect to that non-working session.

lin.chq's profile image lin.chq posted 3 years ago Permalink

There are only these logs

1 attachment(s):
  • -1
ansgar's profile image ansgar posted 3 years ago Permalink

That tells you the SELECT NOW() is causing that error. Never saw that on normal MySQL or MariaDB installations. Must be specific to this HotDB, could that be?

lin.chq's profile image lin.chq posted 3 years ago Permalink

It should be. I made the same mistake with the command line,the SELECT NOW() is causing this error. Is there a solution to this situation? Navicat can be used with normal connection

1 attachment(s):
  • select
lin.chq's profile image lin.chq posted 3 years ago Permalink

That tells you the SELECT NOW() is causing that error. Never saw that on normal MySQL or MariaDB installations. Must be specific to this HotDB, could that be?

I use the command line to specify that the database does not report an error.

Use heidisql to specify a database does not work

1 attachment(s):
  • -
ansgar's profile image ansgar posted 3 years ago Permalink

As you can see in your first screen, SELECT NOW() is also broken with the command line interface, where you don't have a database selected. The issue not specific to HeidiSQL.

I guess you passed a database in the second command line, so the error does not happen then.

This is obviously an issue in that SeaSQL or HotDB MySQL distribution, and should be fixed there, not in HeidiSQL.

lin.chq's profile image lin.chq posted 3 years ago Permalink

But when I select the database in heidisql, I still get an error when it execute the select now().

There is also a problem with HotDB, but we cannot coordinate with them to fix it. We can only see if heidisql can deal with it

lin.chq's profile image lin.chq posted 3 years ago Permalink

As you can see in your first screen, SELECT NOW() is also broken with the command line interface, where you don't have a database selected. The issue not specific to HeidiSQL.

I guess you passed a database in the second command line, so the error does not happen then.

This is obviously an issue in that SeaSQL or HotDB MySQL distribution, and should be fixed there, not in HeidiSQL.

Hi,Could you please help to deal with this problem? Before SELECT NOW() is executed, if the database is specified in heidisql session, can it execute USE DATABASE first? Heidisql is the best I've ever used, and I don't want to give it up,help me,please

1 attachment(s):
  • -_20210501131401
lin.chq's profile image lin.chq posted 3 years ago Permalink

图片如下

lin.chq's profile image lin.chq posted 3 years ago Permalink

图片

1 attachment(s):
  • -_20210501131856
ansgar's profile image ansgar posted 3 years ago Permalink

That setting is just a filter for displayed database(s). It is not used for selecting a database at connection time.

lin.chq's profile image lin.chq posted 3 years ago Permalink

That setting is just a filter for displayed database(s). It is not used for selecting a database at connection time.

Now there is a problem executing SELECT NOW(), other commands no problem

lin.chq's profile image lin.chq posted 3 years ago Permalink

If select now() executes successfully, it will be connect successfully

Please login to leave a reply, or register at first.