Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manticore indexes aren't visible in SSMS object explorer #253

fvuksan opened this issue Jul 17, 2019 · 2 comments


Copy link

commented Jul 17, 2019

I have a problem getting list of databases (indexes) when I register manticore as linked server.
Steps to reproduce:

  1. Create Manticore ODBC datasource using MySQL ODBC 8.0 Unicode driver. Test connection succeeds.

  2. Change MSDASQL provider properties as follows:

  3. Register ODBC datasource as SQL Server linked server

  4. Querying manticore is successful but when I expand linked server in SQL Server Management Studio manticore indexes aren't visible.

When I check query.log I see this line:
/* Mon Jul 15 15:48:04.342 2019 conn 2 */ select database() # error=Sphinx expr: syntax error, unexpected '(', expecting $end near '()'

Windows 10
Microsoft SQL Server 2017 (RTM-GDR) (KB4494351) - 14.0.2014.14 (X64) Apr 5 2019 09:18:51 Copyright (C) 2017 Microsoft Corporation Developer Edition (64-bit) on Windows 10 Pro 10.0 (Build 17134: )


This comment has been minimized.

Copy link

commented Jul 24, 2019

select database() is not supported. In MySQL function DATABASE() is used to return current database as there's USE db syntax. In Manticore Search there's no USE syntax and therefore select database() doesn't make sense too. We can of course fake it to always return NULL or smth.


This comment has been minimized.

Copy link

commented Jul 24, 2019

We can make kind of stub to return reasonable line just to shut up such queries (as already done for many other queries from different connectors, like 'set name=', etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.