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.

Bug in Postgres support for search_path

jamesvl's profile image jamesvl posted 6 years ago in Feature discussion Permalink
Description: trying to use certain features of Postgres (like htables) when using a schema other than 'public' result in Postgres SQL errors.

Expect to see:

Queries which use hstore, when enabled, to succeed.

Actually see:

Error messages saying that public.hstore is not defined.

Core reason:

When 'public' is not part of the current search_path, then extensions defined in public are not able to be used by tables in a different schema.

Details:

I believe Heidi is over-writing the default search_path set by either the database or the user settings. (HeidiSQL is deciding the search path should be limited to *only* the schema they selected in the connection details.) This can lead to unexpected behavior.

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.