Skip to content

support CONVERT( ... USING ...) #133

Closed
@nanawel

Description

@nanawel

Introduction

It seems it's not possible to use the whole range of what MySQL syntax provides for queries.
I stumbled upon a limitation with the statement below.

To Reproduce

SELECT CONVERT("a" USING latin1);

Actual behavior

SQLPage found a syntax error on line 5, character 16:
"a" USING latin1 ) ; 

Expected behavior

This query is perfectly valid on MySQL.

I thought that SQLPage was pretty agnostic to the actual content of the query, and that only the results mattered, but it doesn't seem to be the case and while a query can be perfectly valid for the database server, SQLPage might prevent you to use it.

Is there any other limitations of this kind?
Is it a limitation of the database adapter which does not yet support some MySQL flavors?

Version information

  • Database: MySQL 8
  • SQLPage Version: 0.15.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions