Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

Can't open amended table

muzza4's profile image muzza4 posted 15 years ago in General Permalink
Hi all,

New member here.

I get the message SQL Error: Unknown column 'seasonStart' in 'where clause' when I select the Data tab for the club table.

According to the SQLlog HeidiSQL is running this query ...

SELECT * FROM `club` WHERE Id LIKE '%d14%' <snip> OR seasonStart LIKE '%d14%' <snip>

How do I clear this query so that I can look at this table once again under the Data tab.

By the way, I like HeidiSQL, but it has a number of irritating issues, is a new release planned shortly?

Regards
Muzza
ansgar's profile image ansgar posted 15 years ago Permalink

I get the message SQL Error: Unknown column 'seasonStart' in 'where clause' when I select the Data tab for the club table.



This bug should be fixed and gets included in the next release. And it was posted here as a bug: http://sourceforge.net/tracker/index.php?func=detail&aid=1578471&group_id=164593&atid=832347

By the way, I like HeidiSQL, but it has a number of irritating issues, is a new release planned shortly?



Yes... we are on the way to plan the next release which will come shortly.
muzza4's profile image muzza4 posted 15 years ago Permalink
I searched the registry for "seasonstart" and deleted the 2 entries I found (2 because I have a test database and a live database).

Woohoo.

Thanks
Code modification/commit from ansgar.becker, 9 years ago, revision 4175
TAppSettings.ValueExists respects SessionPath, which is not used in GetSessionNames, so prefer FRegistry.ValueExists here. See http://www.heidisql.com/forum.php?t=11020
Code modification/commit from ansgar.becker, 9 years ago, revision 4176
Give both dropdown and edit box the same width. See http://www.heidisql.com/forum.php?t=11039
Code modification/commit from ansgar.becker, 9 years ago, revision 4183
Fix and enhance handling of multiple statements and multiple results:
* TMySQLConnection.Query did not process further results if the first one is a non-result. Instead, it disconnected you as the required mysql_store_result() was never called. Fixed now. Should fix the error described here: http://www.heidisql.com/forum.php?t=11049
* Cache result of SHOW VARIABLES, and introduce a MaxAllowedPacket function, which benefits from that cache
* Do not limit the number of statements in "batch in one
Code modification/commit from ansgar.becker, 9 years ago, revision 4189
Turn asRecentFilter into a session setting and define its value so it can handle the FormatName parameter. See http://www.heidisql.com/forum.php?t=11096
Code modification/commit from ansgar.becker, 9 years ago, revision 4190
Move some code to TDBConnection.ExplainAnalyzer(), and introduce new query context menu items "Explain current query" and "Explain analyzer for current query". See http://www.heidisql.com/forum.php?t=11036

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




Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.