• Line #736: ERROR: syntax error at or near "s"
• Line #738: ERROR: syntax error at or near "s"
• Line #739: ERROR: syntax error at or near "s"
• Line #744: ERROR: syntax error at or near "s"
• Line #745: ERROR: syntax error at or near "s"
• Line #746: ERROR: syntax error at or near "s"
• Line #747: ERROR: syntax error at or near "s"
• Line #748: ERROR: syntax error at or near "s"
• Line #749: ERROR: syntax error at or near "s"
• Line #750: ERROR: syntax error at or near "s"
• Line #751: ERROR: syntax error at or near "s"
• Line #752: ERROR: syntax error at or near "s"
• Line #753: ERROR: syntax error at or near "s"
• Line #754: ERROR: syntax error at or near "s"
• Line #755: ERROR: syntax error at or near "s"
• Line #756: ERROR: syntax error at or near "s"
• Line #757: ERROR: syntax error at or near "s"
• Line #758: ERROR: syntax error at or near "s"
• Line #759: ERROR: syntax error at or near "s"
• Line #760: ERROR: syntax error at or near "s"
• Line #761: ERROR: syntax error at or near "s"
• Line #762: ERROR: syntax error at or near "s"
• Line #763: ERROR: syntax error at or near "s"
• Line #764: ERROR: syntax error at or near "s"
• Line #765: ERROR: syntax error at or near "s"
• Line #2302: ERROR: syntax error at or near "("
So I manually increased the step in the address bar to see the final page. The forum started to work fine but I am afraid some day it may bump into a problem. Beside that it wasn't a clean install and I am a bit obsessive about that.
What database server? Also, are you running the SQL file directly or letting SMF run it?
Postgres on local machine. I created an empty DB and connected SMF to it.
how were you trying to populate the database?
I saw that actually but what does it mean by replacing \' with "? Should I change the code?
smf 2.1 github version in the case of using postgres.
I have to use 2.0 for the meantime. Though I can change to MySQL.
Your call. I think mod support for pg is spotty.
I haven't installed pg in 2.0, but if I were trying, I'd update the corresponding *.sql file per the instructions in the post referenced above.
or php 7 + pg doesn't work.
or take mysql and accept that this will be not best setup from performance point of view for smf 2.1 (when you upgrade).
That's kind of sad given that 99.99% of all SMF installs aren't on Postgres.
well we use 100% posibilities of mysql 5.0 and raised pg from 30%(30% ~ 100% mysql) to 60%.
So ask mysql that they support more sql function and raise the min mysql version to a reasonable version.
Given these issues, and given that many (most?) mods don't run on pg, I would go with mysql. There is no way to determine pg support by mods that I know of other than trial and error.
I would treat this install is a preview of things to come: lots of code tweaking to get things to work.
the mod support is unknown.
the most work i needed was to get this thing running on smf 2.1.
And two changes was needed to support pg (i had to change native part to smf api calls).
since likes are part of SMF 2.1 that mod should not be installed on SMF 2.1.
i'm not the right person to define if the like system which in smf 2.1 is good or not.
how it look when i want run this under pg.
BTW if this works shouldn't we change the postgres installer in the repo?
Isn't the problem because I didn't set standard_conforming_strings Poetgres option to off before installation as it was mentioned in the manual?