Heidi - For such an intelligent app and then it returns the wrong number of rows!!! Just wow.

[Mashiane]

Hi Fam

I've never used heidi app before but so far its enjoyable. What im really baffled about is the wrong row count it returns.

Perhaps there is some logic to it, where they explaint it, but for someone new into using it, one could get lost very quickly. But I can say I spent a better part of some time trying to "reconcile", then, let me execute a count statement on it. A 3K difference!!! Just wow,

At least now I know that the reliable row count is an actual row count and not the one it will indicate in the app database summary screen.

But why have an actual count for the users table and have everything else wrong for the bigger tables? Baffling.

Actuals:

Old DB Incoming: 34112, Unique Keys: 13280
New DB Incoming: 13280, Unique Keys: 13280
Old DB Incoming: 34112, Unique Keys: 13280
New DB Conversations: 13279, Unique Keys: 13279

I see there's always that one family member out..

 

[tchart]

Heidi is really great as it’s portable. I can’t say I’ve noticed the bad row counts. What is the DBMS? I mainly use it for Postgres.

 

[Sandman]

I find it a bit difficult to parse your message, but have you consider there might simply be a difference in the row count and the next id to be used for the table?

Get next id when I create a new user:

SELECT `auto_increment` FROM INFORMATION_SCHEMA.TABLES WHERE table_name = 'users'
45312

Get number of users:

SELECT count(*) FROM users
45007

The diff is because I've deleted about 300 users. (Obviously not soft-deletes.)

 

[Mashiane]

Heidi is really great as it’s portable. I can’t say I’ve noticed the bad row counts. What is the DBMS? I mainly use it for Postgres.

Yeah, the more I use it the more I am liking it, a lot. Thing is as a new user I really got so confused about the row count that gets displayed when once clicks the database (on the left) and then see the database tab on the right.

This part of the screen I will no longer rely on as a true reflection of the actual rows in my db, because this is giving me false results for MySQL I am using. Thats a lesson that I have just learned in my particular case.

Same result no matter how much I click the refresh button.

Clicking on an individual table (on the left) and then clicking show all on the data tab, tells the true story.

I was migrating my old db to a new db and new schema, so I relied on the database tab "rows" count, as you can see, there is no approximately there. So I assumed the numbers are correct and thought I was doing something absolutely wrong. Then it dawned on me, before I could learn about the show all, that nothing was wrong, after I executed a sql select count(*) call.

It does not make sense that such an awesome app could just give such a false row count, surely that should be standard. Its an awesome app and I will get over this, but I know something I didnt know.

There are 2 roles, its saying zero. I mean whats up with that?

 

[Mashiane]

I find it a bit difficult to parse your message, but have you consider there might simply be a difference in the row count and the next id to be used for the table?

Get next id when I create a new user:

SELECT `auto_increment` FROM INFORMATION_SCHEMA.TABLES WHERE table_name = 'users'
45312

Get number of users:

SELECT count(*) FROM users
45007

The diff is because I've deleted about 300 users. (Obviously not soft-deletes.)

Could be, I dont know, still new with Heidi, but what I experienced just put me off. I will blame it on my windows pc.

 

[aeric]

I started to use HeidiSql many years ago but since I started using Laragon, I use this app less often. I am now using the 1 file php file call adminer. It is much lighter than PhpMyAdmin and provide everything I needed.
On the other point, I don't remember row count is important in a DBMS app.
I am more interested on the row count in my project which is handled by the database engine.

p/s: I think adminer also reporting an estimate of the number of rows or database size. To more accurately getting the row count, I think we should execute SQL count query instead.

edit: Found an explanation.