Use """insert into ParserRule(name)""" instead of """insert into ParserRule(name)"""

[zhaohangbo]

I think it's a bug need to be fixed

By default it's like
 """
insert into ParserRule(
        name,
        conf
      ) values (
        {name},
        {conf}
      )
"""

But we should add the special comma to it
 """
insert into ParserRule(
        `name`,
        `conf`
      ) values (
        {name},
        {conf}
      )
"""

[seratch]

@zhaohangbo I've not figured out what your problem is. What can we do for you on scalikejdbc library side?

[wuranbo]

@seratch desc is the keyword of SQL, this is the problem. So when we has a column name 'desc', the insert sql won't work.

    mysql> create table T(`desc` varchar(255) PRIMARY KEY)
    -> ;
   Query OK, 0 rows affected (0.02 sec)
   mysql> insert into T(desc) VALUES("s");
   ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that  corresponds to your MySQL server version for the right syntax to use near 'desc) VALUES("s")' at line 1

The solution is add ` in any column name in SQL.

[seratch]

@wuranbo If you're talking about QueryDSL feature, there is room for improvement. It's reasonable to enable to automatically enclose columns with backquotes.

But your above examples are simply SQL interpolation or SQL string value. In the case, you can freely use backquotes in your queries.

[wuranbo]

@seratch Thanks for it, wish to see in 3.0.0.
Yes, I mean QueryDSL. The QueryDSL now will not enclose columns with backquotes. So the table T I show above, and @zhaohangbo shows code in our project, will not work with the QueryDSL now. So @zhaohangbo want to fix it by modify the reverse-engine generated code.

[zhaohangbo]

@seratch Thanks for your reply.

The batchInsert() and create() methods in the model, which generated by Reverse Engineering, have a bug needs to be fixed.

In the picture I uploaded above,
the auto-generated SQL by Reverse Engineering:
insert into ParserRule(name, desc) ...... will fail to execute,
because the column name desc is also a key word of MYSQL.

it should be insert into ParserRule(name, desc) ...... to avoid such failure
All the QueryDSL sentences in model generated by Reverse Engineering should add with backquote in case some special words occur in the sentences.

[tototoshi]

I'm using QueryDSL and now in trouble with this problem.

It's reasonable to enable to automatically enclose columns with backquotes.

@seratch Do you have any plan to do this?

[seratch]

@tototoshi Frankly, I myself don't have enough time to work on the implementation right now. If someone properly does a code contribution for it, I'd love to merge it and will release new versions promptly.