Hi,
Quick question. Is there a problem with Couch and SQL 8?
I know when connect to jdbc I need to use this String:
I can't remember which way I installed it, but think I chose backwards compatibility.
Anyway I'm setting up my MacBook - running Mojave.
I have downloaded version 2.1 of Couch and when trying to connect to the database I get the error:
Couldn't connect to database if I leave the host as localhost.
When I change it to 127.0.0.1 it allows me to create the super user but then fails creating some of the tables. See below:
It used to be fine in High Sierra and SQL 5 so think that is the only change. Probably missing something very obvious.
Point out the obvious this is being tested locally before being uploaded to server. The java String is different thing all together.
Quick question. Is there a problem with Couch and SQL 8?
I know when connect to jdbc I need to use this String:
- Code: Select all
jdbc:mysql://192.168.0.4:3306/Travel?autoReconnect=true&useSSL=false
I can't remember which way I installed it, but think I chose backwards compatibility.
Anyway I'm setting up my MacBook - running Mojave.
I have downloaded version 2.1 of Couch and when trying to connect to the database I get the error:
Couldn't connect to database if I leave the host as localhost.
When I change it to 127.0.0.1 it allows me to create the super user but then fails creating some of the tables. See below:
- Code: Select all
Installation failed!
1064: 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 'system int DEFAULT '0', last_failed bigint(11) DEFAULT ' at line 12
CREATE TABLE couch_users ( id int AUTO_INCREMENT NOT NULL, name varchar(255) NOT NULL, title varchar(255), password varchar(64) NOT NULL, email varchar(128) NOT NULL, activation_key varchar(64), password_reset_key varchar(64), registration_date datetime, access_level int DEFAULT '0', disabled int DEFAULT '0', system int DEFAULT '0', last_failed bigint(11) DEFAULT '0', failed_logins int DEFAULT '0', PRIMARY KEY (id) ) ENGINE = InnoDB CHARACTER SET utf8 COLLATE utf8_general_ci;
It used to be fine in High Sierra and SQL 5 so think that is the only change. Probably missing something very obvious.
Point out the obvious this is being tested locally before being uploaded to server. The java String is different thing all together.