heidisql/heidisql

A lightweight client for managing MariaDB, MySQL, SQL Server, PostgreSQL, SQLite, Interbase and Firebird, written in Delphi

HeidiSQL

HeidiSQL is a graphical interface for managing MariaDB or MySQL servers, Microsoft SQL databases, PostgreSQL, SQLite, Interbase or Firebird. "Heidi" lets you browse and edit data, create and edit tables, views, procedures, triggers and scheduled events. Also, you can export structure and data, either to SQL file, clipboard or to other servers. Read about features or see some screenshots.

Need help?

Look at the online help page to learn how to use HeidiSQL. The forum is meant to ask questions. The issue tracker is the place to report bugs or request new features.

Building

Delphi 11.1 is required for building HeidiSQL. Older Delphi versions will most likely fail; newer Delphi versions may work or fail. Unfortunately, Lazarus or one of the other free compilers cannot currently compile HeidiSQL.

Once Delphi is installed, you need to load the SynEdit project from the components folder. Build both run-time and design-time packages. Install the design-time package. Do the same for the VirtualTree component project, and install madExcept.

Afterwards, load the HeidiSQL project from the packages folder.

Translation

If you'd like to contribute by translating HeidiSQL into your mother tongue, you need to register at Transifex, and join an existing language or request a new one.

Contributing to HeidiSQL

• Pull requests will only be accepted for bugfixes. No new features please.
• Please mention a ticket id in your pull request. If there is no ticket for that particular bug yet, go and create an issue request first, and fill out all fields of the issue template.
• To become a developer member, ask Ansgar via email (see https://www.heidisql.com/imprint.php for email address)

Icons8 copyright

Icons added in January 2019 into a TImageCollection component are copyright by Icons8. Used with a special permission from Icons8 given to Ansgar for this project only. Do not copy them for anything else other than building HeidiSQL.

heidisql's Issues

Autocomplete sort order

Expected behavior

Two possible behaviors:

1. autocomplete should sort by alphabetical order (or it should be an option in the settings)
2. autocomplete should complete the text only when I press "enter" and not when I press "space"

Current behavior

Autocomplete does not sort columns, they are displayed in the same order as you have them in the table. Therefore you might pick wrong column name from the popup in certain situations.

Failure information (for bugs)

If you have several columns with similar names, it could lead to autocomplete picking wrong item when you press space-bar.

Steps to reproduce

1. create a table with two columns "column_a" and "column"
2. write a query and have autocomplete to show you suggestions for the table
3. type "column" and press space... your text will be changed to "column_a"

Context

• HeidiSQL version: 9.4.0.5186
• Operating system: Windows 10

Failure Logs

(pressing space at this moment will autocomplete with the "field_b" column name which was not intended)

Add support for materialized views

Expected behavior

For PostgreSQL: Materialized views should show up in either the table tree or the view tree. They should also participate in auto-complete.

Please see:
https://www.heidisql.com/forum.php?t=18944
https://www.heidisql.com/forum.php?t=22652
https://www.heidisql.com/forum.php?t=24348

Current behavior

PostgreSQL's materialized views are not shown in any tree. They do not participate in auto-complete.

Predefined selection in table tools dialog

Expected behavior

Rightclick in database tree of table tools, showing "Select preset" and "Save preset", based on the database node level. (Having it on the server level would prevent this from selecting presets for different database names.)

Current behavior

Selection has to be done manually each time the dialog is shown.

See attached screeny for idea.

Searching numbers is functionally broken

Last reproduced in 9.4.0.5188 though it's been like this since I started using HeidiSQL two years ago.

A bigint column is formatted for example like this:
99 015 124 722 666
which is fine when viewing data, is makes reading it much easier.

If you edit the field, it changes to
99015124722666
No spaces. Fine again.

However, if you want to search for "22666", 0 matches.
Why? Because you actually have to search for "22 666", notice the whitespace.

The digit grouping symbol - whitespace - should be only used for presentation, not when searching!

Default port for PostgreSQL connections should be 5432

Expected behaviour

When creating a new connection, when PostgreSQL is chosen from the "Network Type" drop down menu, the default port should change to 5432, the default port of PostgreSQL.

Current behaviour

The default port is unchanged from the MySQL default port of 3306.
Funnily enough, if you change the drop down menu to SQL Server, you get the default SQL Server port (1433), suggesting that the code to do this exists, just not for PostgreSQL yet.

Steps to reproduce

Please provide detailed steps for reproducing the issue.

1. Start HeidiSQL. Find yourself on the "Session manager" window.
2. Click "New" to create a new connection
3. Change the "Network Type" drop down menu to "PostgreSQL (experimental)".

Context

• HeidiSQL version: 9.4.0.5125 (Portable)
• Database system + version: PostgreSQL 9.6 + PostgreSQL 10
• Operating system: Windows 10 64-bit

EAccessViolation in SynTextDrawer.InitETODist due to logging translated string with critical character

Expected behavior

No error

Current behavior

Error occurs when I execute a query and than another one when I'm clicking on result

Failure information (for bugs)

I have established a connection to remote MySQL v5.6.36 and tried to execute SELECT @@version. Than I have saved a bug report and clicked on result - another error occurred - this one in form of alert wit text "Can't determine the table name" (it's translation - I'm using non-english HeidiSQL)

Steps to reproduce

1. Connect to MySQL db
2. Execute SELECT @@version
3. Click 'Save Bug Report'
4. Click on result row

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5194
• Database system + version: mysql 5.6.36-cll-lve
• Operating system: Windows 8

Failure Logs

Please include any relevant log snippets or files here.
bugreport.txt

Error on disconecting from database with unsaved invalid data

Expected behavior

No error should occur

Current behavior

Error is rising

Failure information (for bugs)

I was having some unsaved raw in a table that was unable to be saved due to some error (I don't remember what it was). Than I have tried to switch to a different db connection and open some table and the error occurred

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5192 (64 Bit)
• Database system + version: MSSQL
• Operating system: Windows 10 Pro v1709 build 16299.64

Failure Logs

In attachments
bugreport.txt

Column default value of uuid_short() for bigint 20 says "Incorrect integer value"

Friends,

I am trying to save table with column having primary key of BIGINT datatype with default value to AUTO_INCREMENT and so far it is working fine. But when i try to set the default value to uuid_short() it throws an alert saying: "SQL Error (1366): Incorrect integer value: 'uuid_short()' for column 'id' at row 1".

HeidiSQL runs the following query:

ALTER TABLE hello_world CHANGE COLUMN id id BIGINT(20) NULL DEFAULT 'uuid_short()' FIRST;

Unquoting uuid_short() works:

ALTER TABLE hello_world CHANGE COLUMN id id BIGINT(20) NULL DEFAULT uuid_short() FIRST;

Can you please allow uuid_short() function to work in default?

Or as a new feature, an option to select function can be added along with existing four options:

1. No default value
2. Custom:
3. NULL
4. AUTO_INCREMENT
5. Function: [NEW] (A list of mariadb functions can be displayed in dropdown for developer to select)

Thank you.

please add mysql table schema

please add mysql table schema like mysql workbench , phpmyadmin ,...

Access violation when opening table with huge ENUM definition

First of all, sorry for my bad English...

Expected behavior

normal display of selected table (data / structure) in HeidiSQL

Current behavior

HeidiSQL crashes (only with some tables)

Failure information (for bugs)

Steps to reproduce

Please provide detailed steps for reproducing the issue.

1. Run attached table creation script
2. try opening the table just created (tbl_tipoprestazione_test), structure or data, no matter
3. HeidiSQL crashes...

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5184 (last working version 8.3.0.4784)
• Database system + version: MySQL 5.6.35 (but not relevant)
• Operating system: Windows 7 Enterprise 32bit

Failure Logs

Heidy does not allow to save the error log (it hangs before), you can only print the attached image.
Thanks for what you can do,
Mauro

CreateTestTable.txt

Need to connect to Bluehost MySQL - how is it established?

Expected behavior

Be able to connect to Bluehost MySQL database for maintenance similar to what phpMyAdmin now permits.

What is the current behavior?

Returns (10060) error

Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.

Just need the procedure to access databases running on MySQL on Bluehost shared servers.

Please provide detailed steps for reproducing the issue.

1. step 1
2. step 2
3. you get it...

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: latest
• Database system + version: bluehost latest
• Operating system: linux (I think)

Failure Logs

Please include any relevant log snippets or files here.

Add shortcut to clear the log

Hello,

A couple of suggestions:

• make available a shortcut (also user customized in Preferences/Shortcuts) to clear the LOG. Suggestion: CTRL + L;

• increase the gutter width of the editor. With the current width the bookmark number and line number are confusing;

• remove from the default shortcuts those that are related to the bookmarks of the SynEdit component: CTRL + NUMBER (to mark) and SHIFT + CTRL + NUMBER (to go). By default 1..5 are related main TabSheet focus.

Best,
J.C.Faria

BLOB data over 0x81 is wrong in result grid view.

Expected behavior

Result of select BLOB data must be same with hex(data) when the query executed.
select data, hex(data) from x_test;

Current behavior

Select result of BLOB data is now different from hex(data).
data : 0x3F -> WRONG!!
hex(data) : 0x81

Failure information (for bugs)

Data 0x80 is ok. not bug.
data : 0x80
hex(data) : 0x80

But 0x81~0xFE data is not ok. it's bug.
data : 0x3F
hex(data) : 0x81

data : 0x3F
hex(data) : 0x82

Steps to reproduce

1. There is a table like below. Create if not exist.

CREATE TABLE x_test (
player_id INT(11) NOT NULL,
data BLOB NOT NULL,
PRIMARY KEY (player_id)
)
COLLATE='utf8_general_ci' ENGINE=InnoDB;

2. Insert HEX data.

INSERT x_test VALUES(1, 0x81);

3. Select data.

SELECT data, HEX(data) FROM x_test;

4. Check the result.

Context

INSERT x_test VALUES(1, 0x81);
INSERT x_test VALUES(2, 0x82);
INSERT x_test VALUES(3, 0x99);
INSERT x_test VALUES(4, 0x8181);
INSERT x_test VALUES(5, 0x818181);
INSERT x_test VALUES(6, 0x81818181);
INSERT x_test VALUES(7, 0x8181818181);
INSERT x_test VALUES(8, 0x818181818181);

• HeidiSQL version: 9.4.0.5191
• Database system + version: 10.0.11-MariaDB
• Operating system: CentOS 6.5

Can't see UNIQUE index

Expected behavior

If there is an index on the table - it should be shown in the Table: tableName tab

Current behavior

Not all indexes are shown in Table: tableName tab

Failure information (for bugs)

I have created an index with an SQL request (because I can't create it with UI due to #51) and now I can't see it in Table: tableName tab

Steps to reproduce

1. Open Query tab for some table and execute

create unique nonclustered index IX_U_payerName_payerEntity ON dbo.[User] (payerName, payerEntity)

In my case the table was named User and it has columns payerName and payerEntity which are NVARCHARs

2. Execute

EXEC sys.sp_helpindex @objname = N'User'

To ensour that index has been created. You should see something like

index_name                 | index_description                                 | index_keys
IX_U_payerName_payerEntity | nonclustered, unique located on PRIMARY           | payerName, payerEntity
PK__user__8372E12F88F72341 | clustered, unique, primary key located on PRIMARY | id

3. Go to Table: tableName tab. Refresh/switch between tables/reconnect - new index is not appearing in the "Indexes" sub tab

Context

• HeidiSQL version: 9.4.0.5192
• Database system + version: Microsoft SQL Server 2016 (SP1-CU2) (KB4013106) - 13.0.4422.0 (X64)
  Express Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 (Build 9600: ) (Hypervisor)
• Operating system: Windows 10

Multiple backtick issues

Expected behavior

Autocomplete should put an ending backtick if you have one in the beginning of the column name. Suggestions should be shown even if I wrap the column name with backticks.

Current behavior

Autocomplete wraps the column name in backticks even if you have already put one backtick by yourself. Also all the suggestions are removed if you start the column name with backtick in the query, but the popup remains open and empty.

Steps to reproduce

1. start typing sql query and have an autocomplete window pop up for available columns
2. start your column name by putting ` (backtick), then type the column name and then press enter
3. you get something like ```column`

Context

HeidiSQL version: 9.4.0.5186
Video of the issue: https://www.youtube.com/watch?v=0A6grLiXB_w
(unfortunately the video does not show the autocomplete popup for some reason, but it's there)

Dark theme for nightly coding sessions

Adding a "dark theme" would be super nice. The white skin is pretty eye straining in some conditions.

You know, for the night operators. ;)

Selects the wrong data

Expected behavior

Hi!
I have the latest version of the program selects the wrong data. (9.4.05191) MySql
The older version displays a normal result.

SQL export includes values for virtual fields

Expected behavior

Exporting SQL to other database without error when table contains virtual column.

Current behavior

MySQL SQL Error (3105) error thrown during SQL export to other database when table contains virtual column.

Failure information (for bugs)

Error message: "SQL Error (3105): The value specified for generated column 'computed_column_name' in table 'table_name' is not allowed."

Snippet for column: is_live TINYINT(1) AS (if(isnull(deleted_at),1,0)) VIRTUAL,

Steps to reproduce

Please provide detailed steps for reproducing the issue.

1. Create a simple table with one generated/computed field and insert some data in it
2. Right-click the table and select "Export database as SQL"
3. Choose any option but "No data" in "Data" field
4. Choose another server or database for "Output"
5. Choose the destination "Database"
6. Click "Export"
7. See error message

Context

• HeidiSQL version: 9.4.0.5185
• Database system + version: MySQL 5.7.18
• Operating system: Windows

The table in question has a column with a simple formula: "AS (columnA + columnB * + columnC)"

Possible solution

The problem that HeidiSQL generates the following command during the Export process that contains the virtual column and values as well: INSERT INTO table (col_1, virtual_col_1) VALUES ('value for col 1', 'value for virtual column');

According to Roy Lyseng the insert command should look like this (without the virtual column): INSERT INTO table (col_1) VALUES ('value for col 1');

Roy wrote that this is not a MySQL bug so it must be handled on the client (HeidiSQL) side.

Workaround

Use triggers instead of virtual columns.

Failure Logs

MySQL exception thrown.

Make Maintenance dialog compatible to MSSQL

Expected behavior

Successful maintenance

Current behavior

Errors marked in Maintenance window, and in log.

Failure information (for bugs)

Steps to reproduce

1. Right click database
2. Click Maintenance
3. Select anything from drop down
4. Click Execute

Context

• HeidiSQL version: 9.4.0.5187 Portable
• Database system + version: SQL Server 2016 Standard.
• Operating system:
  • Database machine: Server 2016 DataCenter
  • Workstation: Windows 10 Pro

Failure Logs

CHECK TABLE "DiasetTags"."dbo"."Histories";
/* SQL Error (156): Incorrect syntax near the keyword 'CHECK'. /
CHECK TABLE "DiasetTags"."dbo"."Parts";
/ SQL Error (156): Incorrect syntax near the keyword 'CHECK'. /
CHECK TABLE "DiasetTags"."dbo"."Settings";
/ SQL Error (156): Incorrect syntax near the keyword 'CHECK'. /
CHECK TABLE "DiasetTags"."dbo"."__MigrationHistory";
/ SQL Error (156): Incorrect syntax near the keyword 'CHECK'. /
ANALYZE TABLE "DiasetTags"."dbo"."Histories";
/ SQL Error (156): Incorrect syntax near the keyword 'TABLE'. /
ANALYZE TABLE "DiasetTags"."dbo"."Parts";
/ SQL Error (156): Incorrect syntax near the keyword 'TABLE'. /
ANALYZE TABLE "DiasetTags"."dbo"."Settings";
/ SQL Error (156): Incorrect syntax near the keyword 'TABLE'. /
ANALYZE TABLE "DiasetTags"."dbo"."__MigrationHistory";
/ SQL Error (156): Incorrect syntax near the keyword 'TABLE'. /
REPAIR TABLE "DiasetTags"."dbo"."Histories";
/ SQL Error (156): Incorrect syntax near the keyword 'TABLE'. /
REPAIR TABLE "DiasetTags"."dbo"."Parts";
/ SQL Error (156): Incorrect syntax near the keyword 'TABLE'. /
REPAIR TABLE "DiasetTags"."dbo"."Settings";
/ SQL Error (156): Incorrect syntax near the keyword 'TABLE'. /
REPAIR TABLE "DiasetTags"."dbo"."__MigrationHistory";
/ SQL Error (156): Incorrect syntax near the keyword 'TABLE'. */

Support for CHARACTER SET for column and procedure parameter

Expected behavior

I would like to have set in GUI different CHARACTER SET for a column and for a procedure parameter.

Current behavior

Cannot set it by GUI. The HeidiSQL allows to change table column COLLATE only.

Context

• HeidiSQL version: 9.4.0.5185
• Database system + version: MariaDB 10.0.31
• Operating system: Windows 10

Regular Expression on Table List Filter

Expected behavior

Using regular expressions on database table list view (Check screenshot)

Current behavior

Feature does not exists yet.

Failure information (for bugs)

Trying to run a regular expression filter on the database filter doesn't work. Trying to filter a certain pattern for the table names (table without numbers) but it doesn't work.

Steps to reproduce

Please provide detailed steps for reproducing the issue.

1. Run HeidiSQL
2. Select any database
3. Once loaded, go to the Database tab
4. Assuming table filter is enabled, add any regular expression to the filter textbox.
5. Regular expression should not run.

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version:
• Database system + version:
• Operating system:

Failure Logs

Screenshot:

Using PROCEDURE ANALYSE() will show encoded result

This query
SELECT * FROM table PROCEDURE ANALYSE();

will generate wrong result. Expected result is text, but I got encoded in hexa.

WIN1250 encoding is handled improperly

I filed a bug report several months ago into the old bug tracking system. In order to keep it alive, I create one for the issue here as well.

Expected behavior

Data from a PostgreSQL database with WIN1250 encoding should be displayed incorrectly.

Current behavior

Accented characters are displayed as wrong characters.

Steps to reproduce

1. I create a new database with encoding win1250:

createdb --encoding=WIN1250 --lc-collate=C --lc-ctype=C --template=template0 heidisql_1250

2. I create some data in it, for example an accented a (á) which is a valid character in win1250:

create table t (c text);
insert into t values (chr(193));

3. Check the content of the table in HeidiSql

In the place where I expect the Hungarian character á to be displayed, I get a questionmark in a diamond.

Context

This happened with the newest version of HeidiSql running on Win7 and PostgreSQL 9.0

Screenshot and previous bug report is available here: https://www.heidisql.com/forum.php?t=23972

Provide column names of selected table in query auto completer

I know this has been discussed before in the forum but i'd really like to see autocompletion for columns inside the Query Editor window without having to prefix everything with table names beforehand.
In the old discussion there were concerns about performance since some users might have databases with thousands of columns and therefore i'd like to offer a compromise:

If you have a table selected in the tree, the columns of the currently selected table are actually available in the list right next to the query editor. So why not add the columns of the currently selected table to the autocompletion list?
PhpMyAdmin actually does this when you use the query tab while working 'inside a table'.
In addition to that you could also add columns from more tables once they're mentioned in the query.
The autocompletion process might also be able to decide to optionally prefix a column with the table name in case it is ambigious.

osx support

RAD Studio supports osx so in theory if we migrate this project to latest version of RAD studio then we can have osx support

i have tried to build HeidiSQL with RAD studio 10.2 but it does not work ...

Hangs on connection if a table is locked

Expected behavior

The software would connect an open normally.

Current behavior

The connnection window jams.

Steps to reproduce

Please provide detailed steps for reproducing the issue.

1. In the first instance, create a table and fill it with lots of data
2. In the second instance, while the first insert datas, try to connect to the DB.
3. you get it...

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.x (latest)
• Database system + version: MariaDB 10.x
• Operating system: WIndows 10.x

Untranslatable words

Expected behavior

Some words/strings are still in English after completing translation. Also some minor problems with UI.

Current behavior

All words/strings should be translated.

Failure information (for bugs)

BTW, there are many words begin with "SEL" near the end of the translation file, what are they for?

CREATE TABLE ... CHECK() . support

Expected behavior

Please add support of CHECK section in create table statement.

Current behavior

No information on UI.
No information about CHECK section in the "CREATE code" tab.

Failure information (for bugs)

Steps to reproduce

CREATE TABLE test_json (
test_col LONGTEXT NULL DEFAULT NULL COLLATE 'utf8mb4_bin'
)
ENGINE=InnoDB;

ALTER TABLE test_json
ADD CHECK(JSON_VALID(test_col));

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: r5184
• Database system + version: MariaDB 10.2.10
• Operating system: Win10

Failure Logs

Please include any relevant log snippets or files here.

Flicker in the editor window when executing SQL

• HeidiSQL version: 9.4.0.5190
• Database system + version: MariaDB
• Operating system: Windows

A flicker in the editor window is visible whenever an SQL statement is executed. I believe this is related to the definition of the parent of TDBGrid created in runtime to display the query result. So, creating an invisible parent on the main screen can be one of the ways to workaround this

Crash on exit, in TMainForm.DisplayRowCountStats

Expected behavior

Crashed on exit

Steps to reproduce

Please provide detailed steps for reproducing the issue.

click on Windows 10 'X' upper right corner of HeidiSQL app
bugreport.txt

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version:
• Database system + version:
• Operating system:

Failure Logs

Please include any relevant log snippets or files here.

Error on creating of a new index

Expected behavior

New index should be created

Current behavior

Error occurs on attempt to create a new index

Failure information (for bugs)

If I create a new index from the UI and then press "Save" an error is occurs an no index is creating. Some error would be for "UNIQUE", "FULLTEXT" and "SPATIAL" types of indexes

Steps to reproduce

Please provide detailed steps for reproducing the issue.

Attempt to create "UNIQUE" index:

1. Open Table: tableName tab
2. Right click on a column name and select "Create a new index" -> "UNIQUE"
3. Click Save

Alert would popup with a text "SQL Error (1081): Incorrect syntax near 'INDEX'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax."

And here is a text from query log:

ALTER TABLE "dbo"."User"
	ADD UNIQUE INDEX "payerName" ("payerName");
/* SQL Error (1018): Incorrect syntax near 'INDEX'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax. */

On attempt to create "FULLTEXT" index errors would be:

Alert: "SQL Error (173): This definition for column 'FULLTEXT' must include a data type"

And query log:

ALTER TABLE "dbo"."User"
	ADD FULLTEXT INDEX "payerName" ("payerName");
/* SQL Error (173): The definition for column 'FULLTEXT' must include a data type. */

On attempt to create "SPATIAL" index errors would be:

The same as for "FULLTEXT" but with "SPATIAL" instead of "FULLTEXT" in error messages

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5192
• Database system + version: Microsoft SQL Server 2016 (SP1-CU2) (KB4013106) - 13.0.4422.0 (X64)
  Express Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 (Build 9600: ) (Hypervisor)
• Operating system: Windows 10

32bit version crashes when closing a PostgreSQL connection

Expected behavior

When I click the close connection button, I expect to be brought back to the session manager.

Current behavior

The program throws an exception. This happens every time I click the close connection button:

Failure information (for bugs)

Steps to reproduce

1. Connect to a PostgreSQL connection.
   • I was unable to test with other databases (MySQL, SQL Server), since I don't have any of those.
2. Click the "Close Connection" button.
3. Exception appears.

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5125 (Portable)
• Database system + version: PostgreSQL 9.6 + PostgreSQL 10
• Operating system: Windows 10 64-bit

Failure Logs

date/time          : 2017-12-11, 08:43:15, 499ms
computer name      : MIKE-DESKTOP
user name          : Mike
registered owner   : Windows User
operating system   : Windows 10 x64 build 16299
system language    : English
system up time     : 5 days 11 hours
program up time    : 3 minutes 56 seconds
processors         : 4x AMD Phenom(tm) II X4 940 Processor
physical memory    : 1096/4095 MB (free/total)
free disk space    : (C:) 81.37 GB
display mode       : 1920x1080, 32 bit
process id         : $1dc4
allocated memory   : 85.00 MB
largest free block : 1.00 GB
executable         : heidisql.exe
exec. date/time    : 2017-12-11 08:33
version            : 9.4.0.5125
compiled with      : Delphi XE5
madExcept version  : 4.0.12
callstack crc      : $c709fa10, $f4c20f33, $f4c20f33
exception number   : 1
exception class    : EAccessViolation
exception message  : Access violation at address 6DBA335C in module 'SSLEAY32.dll'. Read of address C35B5E83.

main thread ($1d94):
6dba335c SSLEAY32.dll                         SSL_shutdown
100052fc libpq.dll                            PQfinish
00847a72 heidisql.exe dbconnection   1985 +47 TPgConnection.SetActive
0095660c heidisql.exe Main           2129 +52 TMainForm.ConnectionsNotify
0086ce7a heidisql.exe dbconnection     38  +0 {System.Generics.Collections}TList<dbconnection.TDBConnection>.Notify
0086daef heidisql.exe dbconnection    728  +0 {System.Generics.Collections}TObjectList<dbconnection.TDBConnection>.Notify
0086ce56 heidisql.exe dbconnection     38  +0 {System.Generics.Collections}TList<dbconnection.TDBConnection>.DoDelete
0086d552 heidisql.exe dbconnection    728  +0 {System.Generics.Collections}TList<dbconnection.TDBConnection>.Delete
0086d525 heidisql.exe dbconnection    728  +0 {System.Generics.Collections}TList<dbconnection.TDBConnection>.Remove
0095625c heidisql.exe Main           2057  +6 TMainForm.actDisconnectExecute
0053b94b heidisql.exe System.Classes          TBasicAction.Execute
00595523 heidisql.exe Vcl.ActnList            TCustomAction.Execute
0053b7eb heidisql.exe System.Classes          TBasicActionLink.Execute
005b154c heidisql.exe Vcl.Controls            TControl.Click
005f80f8 heidisql.exe Vcl.ComCtrls            TToolButton.Click
005b1a0d heidisql.exe Vcl.Controls            TControl.WMLButtonUp
005b100d heidisql.exe Vcl.Controls            TControl.WndProc
005b0c48 heidisql.exe Vcl.Controls            TControl.Perform
005b5268 heidisql.exe Vcl.Controls            GetControlAtPos
005b5332 heidisql.exe Vcl.Controls            TWinControl.ControlAtPos
005b0c48 heidisql.exe Vcl.Controls            TControl.Perform
005b53fc heidisql.exe Vcl.Controls            TWinControl.IsControlMouseMsg
005b59a9 heidisql.exe Vcl.Controls            TWinControl.WndProc
005fcc68 heidisql.exe Vcl.ComCtrls            TToolBar.WndProc
005b5170 heidisql.exe Vcl.Controls            TWinControl.MainWndProc
0053c65c heidisql.exe System.Classes          StdWndProc
774e8c1b USER32.dll                           DispatchMessageW
00686167 heidisql.exe Vcl.Forms               TApplication.ProcessMessage
006861aa heidisql.exe Vcl.Forms               TApplication.HandleMessage
006864e5 heidisql.exe Vcl.Forms               TApplication.Run
76868652 KERNEL32.DLL                         BaseThreadInitThunk

Querying schema with unicode on SQL Server

My table has national character and Heidi is not able to edit its data due to incorrect schema queries

Expected behavior

metadata queries should use unicode strings (N'')

SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA=N'dbo' AND TABLE_NAME=N'Ilości wizyt';
SELECT c.name AS "column", prop.value AS "comment" FROM sys.extended_properties AS prop INNER JOIN sys.all_objects o ON prop.major_id = o.object_id INNER JOIN sys.schemas s ON o.schema_id = s.schema_id INNER JOIN sys.columns AS c ON prop.major_id = c.object_id AND prop.minor_id = c.column_id WHERE prop.name='MS_Description' AND s.name=N'dbo' AND o.name=N'Ilości wizyt';
SELECT C.CONSTRAINT_NAME, C.CONSTRAINT_TYPE, K.COLUMN_NAME FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS AS C INNER JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE AS K ON C.CONSTRAINT_NAME = K.CONSTRAINT_NAME AND K.TABLE_NAME=N'Ilości wizyt' AND K.TABLE_SCHEMA=N'dbo' WHERE C.CONSTRAINT_TYPE IN ('PRIMARY KEY', 'UNIQUE') ORDER BY K.ORDINAL_POSITION;

Current behavior

SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA='dbo' AND TABLE_NAME='Ilości wizyt';
SELECT c.name AS "column", prop.value AS "comment" FROM sys.extended_properties AS prop INNER JOIN sys.all_objects o ON prop.major_id = o.object_id INNER JOIN sys.schemas s ON o.schema_id = s.schema_id INNER JOIN sys.columns AS c ON prop.major_id = c.object_id AND prop.minor_id = c.column_id WHERE prop.name='MS_Description' AND s.name='dbo' AND o.name='Ilości wizyt';
SELECT C.CONSTRAINT_NAME, C.CONSTRAINT_TYPE, K.COLUMN_NAME FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS AS C INNER JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE AS K ON C.CONSTRAINT_NAME = K.CONSTRAINT_NAME AND K.TABLE_NAME='Ilości wizyt' AND K.TABLE_SCHEMA='dbo' WHERE C.CONSTRAINT_TYPE IN ('PRIMARY KEY', 'UNIQUE') ORDER BY K.ORDINAL_POSITION;

it is not possible to edit table's data

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5125
• Database system + version: SQL Server 13.0.4001.0
• Operating system: Windows 7 64b

Cannot create VIEW on MSSQL

Current behavior

When creating a view on MS SQL 11.0 DB, algorithm is set to undefined, but instead of ignoring algorithm in the create statement, it still leaves "ALGORITHM = UNDEFINED" at the beginning of the create. The entire Alg section should be unavailable/grayed out as well for a MSSQL connection.

Failure information (for bugs)

/* SQL Error (343): Unknown object type 'ALGORITHM' used in a CREATE, DROP, or ALTER statement. */

Steps to reproduce

Please provide detailed steps for reproducing the issue.

1. CREATE ALGORITHM = UNDEFINED VIEW "V_ZCUSTOM_AGTDATA" AS .......
2. /* SQL Error (343): Unknown object type 'ALGORITHM' used in a CREATE, DROP, or ALTER statement.*/

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4
• Database system + version: MS SQL 11

Problem with Dark theme - UI and syntax colors

Expected behavior

Syntax highlight coloring must affect on results/gride window also

Current behavior

Syntax highlight coloring does NOT affect on results, so readability of results/gride data is reduced!
(when using dark themes in Windows)

Check the Screenshot
http://s2.zipupload.ir/direct/uid_1_fid3003_1396-09-11_13_22_48_351542258.png

Failure information (for bugs)

None.

Steps to reproduce

1. Change your Windows theme to Dark
2. Open HeidiSQL
3. SELECT some records and look at Result window

Context

• HeidiSQL version: 9.4 (or ANY OTHER VERSION)
• Database system + version: MySQL 5.6
• Operating system: Windows 7 Pro 64-bit

Failure Logs

Results window + Syntax coloring preferences
http://s2.zipupload.ir/direct/uid_1_fid3003_1396-09-11_13_22_48_351542258.png

Make trigger editor compatible to MSSQL

Expected behavior

No error should occur

Current behavior

An error occurred

Steps to reproduce

Please provide detailed steps for reproducing the issue.

I'm not the author of that triggers so I'm not sour what they are inside (I can't open them). I just click on some of them and the error occurs

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5192 (64 Bit)
• Database system + version: MSSQL
• Operating system: Windows 10 Pro v1709 build 16299.64

Failure Logs

I have collect a few crash reports - they are in the attachments
bugreport1.txt
bugreport2.txt
bugreport3.txt

SQLite support

Expected behavior

I would like to see HeidiSQL handle sqlite seamlessly like already supported db.

Current behavior

currently, HeidiSQL can't handle SQLite at all.

Exporting views, generates incorrect SQL DROP statement.

See example bellow, it should be DROP VIEW IF EXISTS:

DROP TABLE IF EXISTS view_test;

CREATE ALGORITHM=UNDEFINED DEFINER=root@localhost SQL SECURITY DEFINER VIEW view_test AS select 123 as abc;

Azure Database for MySQL connection throws error - "SSL connection error: ASN: bad other signature confirmation"

Expected behavior

Connection to the SQL server with no errors

Current behavior

Getting error "SSL connection error: ASN: bad other signature confirmation"

Failure information (for bugs)

This is when adding a SSL CA certificate only (Under the Advanced connection settings)

Microsoft provides SSL connection documentation here:
https://docs.microsoft.com/en-us/azure/mysql/howto-configure-ssl#applications-that-require-a-local-certificate-for-ssl-connectivity

Also, there are already instructions on how to do this with MySQL Workbench:
https://docs.microsoft.com/en-us/azure/mysql/connect-workbench

Steps to reproduce

1. Create a new Azure Database for MySQL database
   (fully hosted/clustered db by Microsoft Azure - https://azure.microsoft.com/en-us/services/mysql/)
2. Download the SSL CA that Microsoft provides, here:
   https://docs.microsoft.com/en-us/azure/mysql/howto-configure-ssl
3. Next, in HeidiSql, create a new connection and point to the new Azure database (created in step 1)
4. While still creating your connection, switch to the Advanced tab to setup the SSL
5. In the Advanced tab, add the SSL CA certificate that was just downloaded (only this file-field should be filled in).
6. Save and Open the connection
7. Get error

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4.0.5125 (64-bit)
• Database system + version: Azure Database for MySQL
• Operating system: Windows 10 Pro 64-bit (Fall Creators Update)

Failure Logs

SSL connection error: ASN: bad other signature confirmation

EStringListError: List index out of bounds (37)

I was dropping some databases. After I already dropped some, HeidiSQL crashed when I selected another one.

Failure information

date/time          : 2017-12-07, 23:38:55, 277ms
computer name      : foo
user name          : bar
registered owner   : bar / foo
operating system   : Windows 7 x64 Service Pack 1 build 7601
system language    : German
system up time     : 12 hours 41 minutes
program up time    : 1 minute 13 seconds
processors         : 8x Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
physical memory    : 22333/32644 MB (free/total)
free disk space    : (C:) 12,12 GB
display mode       : 1920x1200, 32 bit
process id         : $21bc
allocated memory   : 75,31 MB
largest free block : 8185,56 GB
executable         : heidisql.exe
exec. date/time    : 2017-12-06 04:14
version            : 9.4.0.5191
compiled with      : Delphi XE5
madExcept version  : 4.0.12
callstack crc      : $7bc6b9d5, $8e5a7035, $8e5a7035
exception number   : 1
exception class    : EStringListError
exception message  : List index out of bounds (37).

main thread ($18a8):
00587470 heidisql.exe   System.Classes            .TStringList
7fefd55a KERNELBASE.dll                           RaiseException
0040e940 heidisql.exe   System                    @RaiseAtExcept
005b718c heidisql.exe   System.Classes            TStrings.Error
005b9cf2 heidisql.exe   System.Classes            TStringList.Get
00c728dc heidisql.exe   Main            9421   +5 TMainForm.ListDatabasesGetText
00903547 heidisql.exe   VirtualTrees   33561   +8 TCustomVirtualStringTree.DoGetText
00901d64 heidisql.exe   VirtualTrees   33023   +4 TCustomVirtualStringTree.GetText
00903457 heidisql.exe   VirtualTrees   33545  +26 TCustomVirtualStringTree.DoGetNodeWidth
008df08d heidisql.exe   VirtualTrees   18684  +83 TBaseVirtualTree.DetermineHitPositionLTR
008f3e3c heidisql.exe   VirtualTrees   27294 +105 TBaseVirtualTree.GetHitTestInfoAt
008e63bc heidisql.exe   VirtualTrees   21789   +4 TBaseVirtualTree.HandleHotTrack
008ea5b3 heidisql.exe   VirtualTrees   23376  +86 TBaseVirtualTree.MouseMove
006959e4 heidisql.exe   Vcl.Controls              TControl.WMMouseMove
0040cb1e heidisql.exe   System                    TObject.Dispatch
00694b83 heidisql.exe   Vcl.Controls              TControl.WndProc
0069c24e heidisql.exe   Vcl.Controls              TWinControl.WndProc
008ef41e heidisql.exe   VirtualTrees   25273  +32 TBaseVirtualTree.WndProc
0069b48a heidisql.exe   Vcl.Controls              TWinControl.MainWndProc
005dbdc3 heidisql.exe   System.Classes            StdWndProc
76ca98bd USER32.dll                               DispatchMessageW
0081469f heidisql.exe   Vcl.Forms                 TApplication.ProcessMessage
00814713 heidisql.exe   Vcl.Forms                 TApplication.HandleMessage
00814bff heidisql.exe   Vcl.Forms                 TApplication.Run
00ca0277 heidisql.exe   heidisql          80  +24 initialization
76da59cb kernel32.dll                             BaseThreadInitThunk

Steps to reproduce

Well, once I restarted HeidiSQL after the crash I continued dropping the remaining databases but HeidiSQL didn't crash again. So I am not sure if this is reproducible.

What I did exactly when HeidiSQL crashed the first time

1. I started HeidiSQL
2. When "Session Manager" appeared I double clicked a session which connects via SSH tunnel to a remote MariaDB server.
3. HeidiSQL main window appeared:

4. I tried to delete the databases via the right pane using the "Databases" tab. Therefore I clicked the "Database" column to change sort order.
5. Once I noticed I cannot delete from this view (context menu after right clicking on a database entry in the list didn't show a DROP action) I used the left pane, opened the context menu for the database I wanted to drop and selected "Drop ..." and confirmed. This worked fine.
6. I repeated step 5 twice and when I tried to drop the 4th database in a row, HeidiSQL suddenly crashed.

Autocomplete freezes GUI

Steps to reproduce

1. Connect to a MariaDB.
2. Run a long time query, e.g.:
   select sleep(120);
3. Start typing a new query in the editor. At some point, the HeidiSQL tries to autocomplete the column names and the GUI freezes until the first query finishes.

Expected behavior

Do not freeze the GUI. I suppose either one of:

• Use separate DB connection for fetching the DB metadata.
• Freeze the editor only, not the whole GUI, so as it is possible to cancel the query (ESC).
• Disable autocomplete and other operations requiring the metadata when a query is running. (This is the least convenient, since the query may finish soon.)

Context

• HeidiSQL version: 9.4.0.5185
• Database system + version: MariaDB 10.0.31
• Operating system: Windows 10

Problem with doublequotes in column names

I have a software which automatically creates a MySQL table with doublequotes in the column name, and I can't change this behavior.

HeidiSQL has problems to handle those columns correctly.

Using the MySQL command line client, it is no problem to run this code:

 CREATE TABLE TestLog (
  `myInt` INT,
  `"myFunnyFloat"` FLOAT,
  `"myFunnyString"` VARCHAR(30),
  `"myFunnyInt"` INT,
  `"myFunnyDateTime"` DATETIME
) ENGINE=InnoDB

INSERT INTO TestLog VALUES ('42', '3.141', 'Hello Heidi', '21', '2017-12-14 10:00:00');

SELECT * FROM testlog;
+-------+----------------+-----------------+--------------+---------------------+
| myInt | "myFunnyFloat" | "myFunnyString" | "myFunnyInt" | "myFunnyDateTime"   |
+-------+----------------+-----------------+--------------+---------------------+
|    42 |          3.141 | Hello Heidi     |           21 | 2017-12-14 10:00:00 |
+-------+----------------+-----------------+--------------+---------------------+
1 row in set (0.00 sec)

In HeidiSQL, one can create the table this way, too, but inserting the data fails.
Further more, all columns are displayed blue like integers in the data tab, and apart from the first column, there is no column name. The data itself is displayed as

42 | 3.141 | He.llo. He.idi | 21 | 2.017.-12.-14. 10.:00.:00

which is somewhat weird.

(I'd insert a screenshot here, but Github doesn't let me)

HeidiSQL indeed thinks those columns are INTs without names, as its own CREATE-code shows:

CREATE TABLE `testlog` (
	`myInt` INT(11) NULL DEFAULT NULL,
	`` INT NULL,
	`` INT NULL,
	`` INT NULL,
	`` INT NULL
)
COLLATE='latin1_swedish_ci'
ENGINE=InnoDB;

Playing with this issue shows that for each row with doublequotes in its column name, HeidiSQL deletes the column name and assigns the data type of the last row without doublequotes.

Keep table tree open when refreshing table list

When create new tables, I often fresh the structure of all tables by pressing F5.
This enhancement was on HeidiSQL forum and +1ed twice (https://www.heidisql.com/forum.php?t=21627#p24206)

Expected behavior

When the database is selected and you press F5, the list is refreshed without having to do an extra operation

Current ehavior

When the database is selected and you press F5, all the table list is collapsed and it forces you to reopen it.

Steps to reproduce

1. Select a database
2. Press F5

EOutOfMemory crash when exporting grid with huge result

Just wanted to send you a Bug Report that was shown to me by the application.

Background

Ran a SELECT query on the table.
Received the expected results.
Tried to export the grid.
The application showed the bug report.
exception class : EOutOfMemory
exception message : Out of memory.

Failure information (for bugs)

date/time : 2017-11-30, 10:56:25, 572ms
computer name : XXXX
user name : XXXX
registered owner : XXXX
operating system : Windows 7 x64 Service Pack 1 build 7601
system language : English
system up time : 1 day 19 hours
program up time : 1 hour 13 minutes
processors : 4x Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
physical memory : 7923/16080 MB (free/total)
free disk space : (C:) 4.37 GB
display mode : 1600x900, 32 bit
process id : $3e4c
allocated memory : 768.39 MB
largest free block : 210.25 MB
executable : heidisql.exe
exec. date/time : 2016-10-21 13:41
version : 9.4.0.5125
compiled with : Delphi XE5
madExcept version : 4.0.12
callstack crc : $d522dc1c, $fb3dc0d6, $fb3dc0d6
exception number : 1
exception class : EOutOfMemory
exception message : Out of memory.

main thread ($1da0):
0040c8ed heidisql.exe System 196 +0 DynArraySetLength
0040ca19 heidisql.exe System 196 +0 @DynArraySetLength
0052b247 heidisql.exe System.Classes TBytesStream.Realloc
0052b025 heidisql.exe System.Classes TMemoryStream.SetCapacity
0052b171 heidisql.exe System.Classes TMemoryStream.Write
0052b628 heidisql.exe System.Classes TStringStream.WriteString
0090e3c5 heidisql.exe exportgrid 882 +409 TfrmExportGrid.btnOKClick
005b1563 heidisql.exe Vcl.Controls TControl.Click
005d3f42 heidisql.exe Vcl.StdCtrls TCustomButton.Click
005d4abc heidisql.exe Vcl.StdCtrls TCustomButton.CNCommand
005b100d heidisql.exe Vcl.Controls TControl.WndProc
005b5b2d heidisql.exe Vcl.Controls TWinControl.WndProc
005d3bec heidisql.exe Vcl.StdCtrls TButtonControl.WndProc
005b0c48 heidisql.exe Vcl.Controls TControl.Perform
005b5c93 heidisql.exe Vcl.Controls DoControlMsg
005b6723 heidisql.exe Vcl.Controls TWinControl.WMCommand
0067fc8c heidisql.exe Vcl.Forms TCustomForm.WMCommand
005b100d heidisql.exe Vcl.Controls TControl.WndProc
005b5b2d heidisql.exe Vcl.Controls TWinControl.WndProc
0067ca99 heidisql.exe Vcl.Forms TCustomForm.WndProc
005b5170 heidisql.exe Vcl.Controls TWinControl.MainWndProc
0053c65c heidisql.exe System.Classes StdWndProc
77dd0117 ntdll.dll KiUserCallbackDispatcher
76a696c0 USER32.dll SendMessageW
76a70d60 USER32.dll CallWindowProcW
005b5c3e heidisql.exe Vcl.Controls TWinControl.DefaultHandler
005b19b8 heidisql.exe Vcl.Controls TControl.WMLButtonUp
005b100d heidisql.exe Vcl.Controls TControl.WndProc
005b5b2d heidisql.exe Vcl.Controls TWinControl.WndProc
005d3bec heidisql.exe Vcl.StdCtrls TButtonControl.WndProc
005b5170 heidisql.exe Vcl.Controls TWinControl.MainWndProc
0053c65c heidisql.exe System.Classes StdWndProc
76a67885 USER32.dll DispatchMessageW
00686167 heidisql.exe Vcl.Forms TApplication.ProcessMessage
006861aa heidisql.exe Vcl.Forms TApplication.HandleMessage
00681516 heidisql.exe Vcl.Forms TCustomForm.ShowModal
0095a29d heidisql.exe Main 2966 +4 TMainForm.actExportDataExecute
0053b94b heidisql.exe System.Classes TBasicAction.Execute
00595523 heidisql.exe Vcl.ActnList TCustomAction.Execute
0053b7eb heidisql.exe System.Classes TBasicActionLink.Execute
0066c19b heidisql.exe Vcl.Menus TMenuItem.Click
0066d807 heidisql.exe Vcl.Menus TMenu.DispatchCommand
0066ea76 heidisql.exe Vcl.Menus TPopupList.WndProc
005b5170 heidisql.exe Vcl.Controls TWinControl.MainWndProc
0066e9c5 heidisql.exe Vcl.Menus TPopupList.MainWndProc
0053c65c heidisql.exe System.Classes StdWndProc
76a67885 USER32.dll DispatchMessageW
00686167 heidisql.exe Vcl.Forms TApplication.ProcessMessage
006861aa heidisql.exe Vcl.Forms TApplication.HandleMessage
006864e5 heidisql.exe Vcl.Forms TApplication.Run
76b63368 kernel32.dll BaseThreadInitThunk

Editor: increase gutter width

Please, increase the gutter width of the editor. With the current width the bookmark number and line number are confusing.

Make User Manager compatible to MSSQL

Expected behavior

Some form of means to edit users/permissions on the SQL server.

Current behavior

Error dialog saying "SQL Error (156): Incorrect syntax near the keyword 'LIKE'.

Failure information (for bugs)

Not much to put here.

Steps to reproduce

1. Connect to server as sa
2. Click database.
3. Tools > User Manager
4. boom.

Context

• HeidiSQL version: 9.4.0.5187 Portable
• Database system + version: SQL Server 2016 Standard.
• Operating system:
  • Database machine: Server 2016 DataCenter
  • Workstation: Windows 10 Pro

Failure Logs

SHOW VARIABLES LIKE 'skip_name_resolve';
/* SQL Error (156): Incorrect syntax near the keyword 'LIKE'. */

Can't change new line type

Expected behavior

Change new line type from Windows to Unix

Current behavior

Crash

Steps to reproduce

1. Open VARCHAR value editor.
2. Try change line endings to unix

Failure Logs

date/time          : 2017-12-16, 13:54:34, 434ms
computer name      : DESKTOP
user name          : kamcio96 <admin>
registered owner   : Użytkownik systemu Windows
operating system   : Windows 10 x64 build 15063
system language    : Polish
system up time     : 21 days 2 hours
program up time    : 1 minute 15 seconds
processors         : 4x Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
physical memory    : 1363/7974 MB (free/total)
free disk space    : (C:) 438,93 GB
display mode       : 1920x1080, 32 bit
process id         : $5bc
allocated memory   : 71,41 MB
largest free block : 131029,99 GB
executable         : heidisql.exe
exec. date/time    : 2017-12-16 13:53
version            : 9.4.0.5193
compiled with      : Delphi XE5
madExcept version  : 4.0.12
callstack crc      : $c5601809, $061da0d0, $061da0d0
exception number   : 1
exception class    : EAccessViolation
exception message  : Access violation at address 0000000000AE1FB2 in module 'heidisql.exe'. Read of address 0000000000000078.

main thread ($3440):
00ae1fb2 heidisql.exe texteditor      130 +15 TfrmTextEditor.SelectLinebreaks
007eb6a9 heidisql.exe Vcl.Menus               TMenuItem.Click
007edfbf heidisql.exe Vcl.Menus               TMenu.DispatchCommand
007f0514 heidisql.exe Vcl.Menus               TPopupList.WndProc
007f0415 heidisql.exe Vcl.Menus               TPopupList.MainWndProc
005dbdc3 heidisql.exe System.Classes          StdWndProc
7ff8bb03 USER32.dll                           DispatchMessageW
0081469f heidisql.exe Vcl.Forms               TApplication.ProcessMessage
00814713 heidisql.exe Vcl.Forms               TApplication.HandleMessage
0080d058 heidisql.exe Vcl.Forms               TCustomForm.ShowModal
00aeb771 heidisql.exe grideditlinks  1130  +7 TInplaceEditorLink.ButtonClick
00695444 heidisql.exe Vcl.Controls            TControl.Click
006ccd66 heidisql.exe Vcl.StdCtrls            TCustomButton.Click
006cdd82 heidisql.exe Vcl.StdCtrls            TCustomButton.CNCommand
0040cb1e heidisql.exe System                  TObject.Dispatch
00694b83 heidisql.exe Vcl.Controls            TControl.WndProc
0069c24e heidisql.exe Vcl.Controls            TWinControl.WndProc
006cc7b0 heidisql.exe Vcl.StdCtrls            TButtonControl.WndProc
00694660 heidisql.exe Vcl.Controls            TControl.Perform
0069c449 heidisql.exe Vcl.Controls            DoControlMsg
0069d7c3 heidisql.exe Vcl.Controls            TWinControl.WMCommand
0040cb1e heidisql.exe System                  TObject.Dispatch
00694b83 heidisql.exe Vcl.Controls            TControl.WndProc
0069c24e heidisql.exe Vcl.Controls            TWinControl.WndProc
0069b48a heidisql.exe Vcl.Controls            TWinControl.MainWndProc
005dbdc3 heidisql.exe System.Classes          StdWndProc
7ff8bc59 ntdll.dll                            KiUserCallbackDispatcher
7ff8bb03 USER32.dll                           SendMessageW
7ff8bb03 USER32.dll                           CallWindowProcW
0069c3e9 heidisql.exe Vcl.Controls            TWinControl.DefaultHandler
00695aec heidisql.exe Vcl.Controls            TControl.WMLButtonUp
0040cb1e heidisql.exe System                  TObject.Dispatch
00694b83 heidisql.exe Vcl.Controls            TControl.WndProc
0069c24e heidisql.exe Vcl.Controls            TWinControl.WndProc
006cc7b0 heidisql.exe Vcl.StdCtrls            TButtonControl.WndProc
0069b48a heidisql.exe Vcl.Controls            TWinControl.MainWndProc
005dbdc3 heidisql.exe System.Classes          StdWndProc
7ff8bb03 USER32.dll                           DispatchMessageW
0081469f heidisql.exe Vcl.Forms               TApplication.ProcessMessage
00814713 heidisql.exe Vcl.Forms               TApplication.HandleMessage
00814bff heidisql.exe Vcl.Forms               TApplication.Run
00ca02c7 heidisql.exe heidisql         80 +24 initialization
7ff8bc2d KERNEL32.DLL                         BaseThreadInitThunk
7ff8bc56 ntdll.dll                            RtlUserThreadStart

Replace default shortcuts CTRL + 1..5

Please, remove from the default shortcuts those related to go to bookmarks of the SynEdit component. By default CTRL + 1..5 are set to change the main TabSheet focus, forcing the user to use only the restricted set of CTRL + 6..9.

Select multiple rows of one or more columns

Expected behavior

can support the select some area in the result like excel?
like this

Current behavior

Because I just can copy the result which selected.

and when I have to copy more data , I have to export to clipboard and use editor to edit the data.

Can this improve?

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• HeidiSQL version: 9.4
• Database system + version: mysql 5.0.96
• Operating system:Windows 10

1215: “Cannot add foreign key constraint” Problem

I have tried many methods, considering that this error is from column mismatch, but the problem is that the line format is not set as default. The line format should automatically be dynamic when exporting a foreign key.

I've been through this for 1 day. When I realized that I could not fix it on HeidiSQL, I switched to the Navicat program and assigned a foreign key and observed that it was active without problems. The reason that it was active was that the line format was set to DYNAMIC.

I use Google Translate...