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

Error in log on Django connection #2204

Open
8 tasks
tarkhil opened this issue May 20, 2024 · 1 comment
Open
8 tasks

Error in log on Django connection #2204

tarkhil opened this issue May 20, 2024 · 1 comment

Comments

@tarkhil
Copy link

tarkhil commented May 20, 2024

Bug Description:

                SELECT VERSION(),
                       @@sql_mode,
                       @@default_storage_engine,
                       @@sql_auto_is_null,
                       @@lower_case_table_names,
                       CONVERT_TZ('2001-01-01 01:00:00', 'UTC', 'UTC') IS NOT NULL
             # error=P01: syntax error, unexpected IS near 'IS NOT NULL

upon connection by Django. As far as I understand, CONVERT_TZ('2001-01-01 01:00:00', 'UTC', 'UTC') IS NOT NULL is a valid SQL, or manticore is assumed not to understand it?

Manticore Search Version:

6.2.12 dc5144d@230822 (columnar 2.2.4 5aec342@230822) (secondary 2.2.4 5aec342@230822)

Operating System Version:

Ubuntu 22.04.3 LTS

Have you tried the latest development version?

  • Yes

Internal Checklist:

To be completed by the assignee. Check off tasks that have been completed or are not applicable.

  • Task estimated
  • Specification created, reviewed, and approved
  • Implementation completed
  • Tests developed
  • Documentation updated
  • Documentation proofread
  • Changelog updated
@tarkhil tarkhil added the bug label May 20, 2024
@sanikolaev
Copy link
Collaborator

CONVERT_TZ() has nothing to do with Manticore. @tarkhil, do you mean that you tried to use Manticore instead of MySQL in Django and it failed? Unfortunately, not every tool designed for use with MySQL is compatible with Manticore.

Another related issue is #670

@sanikolaev sanikolaev removed the bug label May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants