SMF 2.0.19 to EA 1.1.18 problem

Topic: SMF 2.0.19 to EA 1.1.18 problem (Read 939 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

SMF 2.0.19 to EA 1.1.18 problem

February 10, 2022, 09:47:11 am

Everything works fine except:

This query:

QuoteREPLACE INTO database1.ea_custom_fields
(col_name, field_name, field_desc, field_type, field_length, field_options, mask, show_reg, show_display, show_profile, private, active, bbc, can_search, default_value, enclose, placement, rows, cols)
VALUES('cust_gender', 'Gender', 'Your gender', 'radio', 15, 'undisclosed,male,female,genderless,nonbinary,transgendered', '', 0, 1, 'forumprofile', 0, 1, 0, 0, 'undisclosed', '', 0, 0, 0);

Caused the error:

QuoteYou have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'rows, cols)
VALUES('cust_gender', 'Gender', 'Your gender', 'radio', 15, '...' at line 2

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #1 – February 11, 2022, 03:47:01 am

I believe that is because MariaDB added the "rows" name as reserved as of 10.2.4. So that query would need to be updated to use a fully qualified reference like database1.ea_custom_fields.rows

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #2 – February 11, 2022, 10:11:48 am

Quote from: Spuds – February 11, 2022, 03:47:01 amI believe that is because MariaDB added the "rows" name as reserved as of 10.2.4. So that query would need to be updated to use a fully qualified reference like database1.ea_custom_fields.rows

Hm ... I don't think so. After all, the installation process of ElkArte uses the same SQL query. And it runs even without error message.

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #3 – February 11, 2022, 11:29:45 am

You need the ‘’ around the rows keyword, in the actual insert query part.

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #4 – February 11, 2022, 12:32:23 pm

Quote from: tino – February 11, 2022, 11:29:45 amYou need the ‘’ around the rows keyword, in the actual insert query part.

Just tested the query with ' and " around rows. Same error. :'(

EDIT: cry emo does not compute! ;)

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #5 – February 11, 2022, 12:56:37 pm

I just truncated the SQL query after 'placement', as well as the values. Works.

After that 'rows, cols' in a separate query. Does not work.

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #6 – February 11, 2022, 01:50:53 pm

It’s not the ' mark you have to use, but the ` mark. They’re visually similar but they mean different things…

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #7 – February 11, 2022, 02:02:36 pm

Quote from: Arantor – February 11, 2022, 01:50:53 pmIt’s not the ' mark you have to use, but the ` mark. They’re visually similar but they mean different things…

As Arantor said the backtick, it seems typing from my phone has changed it to a ‘ so apologies. This is MySQL only mind, Postgres doesn’t support it.

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #8 – February 11, 2022, 03:21:26 pm

Ah ... now, yes... worked. Or as they say here casually: Now it becomes a shoe.
But why does the installation of ElkArte work without errors? Is the quotation mark already implemented there?

@Tino With my autocorrect apostrophes or quotation marks are also sometimes degraded to commas.

Re: SMF 2.0.19 to EA 1.1.18 problem

Reply #9 – February 13, 2022, 09:46:28 am

Time to relax on Sunday morning. Added the "backtick" in the smf2-0_importer.xml file about line 780 three times around the "rows". The data transfer from SMF 2.0.19 has now worked fine.

For interested the file in the attachment.