46
ThumbsPlus v7-v9 Questions / TP7 to TP9 conversion fails
« on: 2015-04-01 13:35:32 »
does anyone have any thoughts on this problem??
User Forums
News:
User forums now online! Please see the latest post in the Announcements forum for more information.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
47
ThumbsPlus v7-v9 Questions / TP7 to TP9 conversion fails
« on: 2015-01-13 15:55:51 »
Hello,
I have a working version of TP7 in MariaDB. I downloaded the trial version of TP9, and used the following menu items - "database,advanced,convert client/server". for options, I choose "open converted database. I did not choose "bypass user check" because it says "v7 users will crash" in the program dialog. I hit start and get the following error. can anyone advise how to progress this?
I have a working version of TP7 in MariaDB. I downloaded the trial version of TP9, and used the following menu items - "database,advanced,convert client/server". for options, I choose "open converted database. I did not choose "bypass user check" because it says "v7 users will crash" in the program dialog. I hit start and get the following error. can anyone advise how to progress this?
48
ThumbsPlus v7-v9 Questions / TP7 : what's required to open MYSQL db
« on: 2014-08-28 17:58:55 »
hello all,
still wrestling with my inability to open restored TP7 db to TP sp2. let me ask this question.
what is required for TP7 to successfully open the MYSQL db. here's what I'm aware of. am I missing anything??
(a) a 32 bit ODBC connector. I have 32 bit ODBC installed and can successfully connect to the database within the ODBC dialog box.
(b) sql mode = ANSI
(c) a valid MySQL TP 7 database - I used the script on the Cerious website. only modification is to change "type" to "engine" since "type" is now deprecated in current version. I can see my data in Workbench.
(d) table databaseinfo populated with valid data
in my case, I have each of these as shown below. in fact, I can successfully look at the TP7 database in workbench with my data in it. what could I be missing??
still wrestling with my inability to open restored TP7 db to TP sp2. let me ask this question.
what is required for TP7 to successfully open the MYSQL db. here's what I'm aware of. am I missing anything??
(a) a 32 bit ODBC connector. I have 32 bit ODBC installed and can successfully connect to the database within the ODBC dialog box.
(b) sql mode = ANSI
(c) a valid MySQL TP 7 database - I used the script on the Cerious website. only modification is to change "type" to "engine" since "type" is now deprecated in current version. I can see my data in Workbench.
(d) table databaseinfo populated with valid data
in my case, I have each of these as shown below. in fact, I can successfully look at the TP7 database in workbench with my data in it. what could I be missing??
49
ThumbsPlus v7-v9 Questions / tp7 to tp9 conversion
« on: 2014-08-27 21:04:53 »
hello all,
I've downloaded tp9 and am attempting to convert tp7 MYSQL db to tp9. in doing this, I'm getting the below error message (partial since I hit the 5000 character limit). any thoughts on how to fix this.
======================================================
Opening database for conversion.
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
[Microsoft][ODBC Driver Manager] Function sequence error
[Microsoft][ODBC Driver Manager] Function sequence error
Identifying database...
Database server type is MySQL.
Mappings: {u'TEXT': u'longtext', u'COUNTER': u'int(11) not null primary key auto_increment', u'FLAG': u'bit', u'INT64': u'bigint(20)', u'DATE': u'varchar(32)', u'ID': u'int(11)', u'INT32': u'int(11)', u'INT16': u'smallint(5)', u'BIN64': u'tinyblob', u'BLOB': u'longblob', u'WCHAR': u'varchar'}
Removing pre-v7 cruft.
Exec (nocheck): drop table [ActiveUsers]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
Exec (nocheck): drop table [CurrentUsers]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"CurrentUsers"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"CurrentUsers"' at line 1
Exec (nocheck): drop table [Logins]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"Logins"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"Logins"' at line 1
Exec (nocheck): drop table [DoesPathHaveThumbs]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"DoesPathHaveThumbs"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"DoesPathHaveThumbs"' at line 1
Exec (nocheck): drop table [GalleryThumbStart]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"GalleryThumbStart"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"GalleryThumbStart"' at line 1
Exec (nocheck): drop table [GetThumbnail]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use nea
Best Regards,
David Meinert
I've downloaded tp9 and am attempting to convert tp7 MYSQL db to tp9. in doing this, I'm getting the below error message (partial since I hit the 5000 character limit). any thoughts on how to fix this.
======================================================
Opening database for conversion.
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
[Microsoft][ODBC Driver Manager] Function sequence error
[Microsoft][ODBC Driver Manager] Function sequence error
Identifying database...
Database server type is MySQL.
Mappings: {u'TEXT': u'longtext', u'COUNTER': u'int(11) not null primary key auto_increment', u'FLAG': u'bit', u'INT64': u'bigint(20)', u'DATE': u'varchar(32)', u'ID': u'int(11)', u'INT32': u'int(11)', u'INT16': u'smallint(5)', u'BIN64': u'tinyblob', u'BLOB': u'longblob', u'WCHAR': u'varchar'}
Removing pre-v7 cruft.
Exec (nocheck): drop table [ActiveUsers]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"ActiveUsers"' at line 1
Exec (nocheck): drop table [CurrentUsers]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"CurrentUsers"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"CurrentUsers"' at line 1
Exec (nocheck): drop table [Logins]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"Logins"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"Logins"' at line 1
Exec (nocheck): drop table [DoesPathHaveThumbs]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"DoesPathHaveThumbs"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"DoesPathHaveThumbs"' at line 1
Exec (nocheck): drop table [GalleryThumbStart]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"GalleryThumbStart"' at line 1
<1064•42000>
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]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 '"GalleryThumbStart"' at line 1
Exec (nocheck): drop table [GetThumbnail]
[MySQL][ODBC 5.3(a) Driver][mysqld-5.6.20]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use nea
Best Regards,
David Meinert
50
ThumbsPlus v7-v9 Questions / ThumbsPlus 7 : MySQL database : Part 1
« on: 2014-08-25 19:01:56 »
Sjoinca,
thank you for the response. well, I've gotten everything installed as per the versions you've shared and I'm still getting the same error. very frustrating. I can see the tables fine in workbench. I can write SQL queries against the tables and they work fine. the TP7 sp2 software still thinks something is wrong.
any other thoughts from anyone???
are there any diagnostics I can do to chase this? I've posted part of the ODBC log. would the entire log be of benefit?
let me add another thought. since my machine crashed, I had to reload the operating system to factory image. I named my computer exactly the same; but I'm wondering if some of the stuff in the volume table is causing a problem (ie: serialno, netname, etc??)
David
thank you for the response. well, I've gotten everything installed as per the versions you've shared and I'm still getting the same error. very frustrating. I can see the tables fine in workbench. I can write SQL queries against the tables and they work fine. the TP7 sp2 software still thinks something is wrong.
any other thoughts from anyone???
are there any diagnostics I can do to chase this? I've posted part of the ODBC log. would the entire log be of benefit?
let me add another thought. since my machine crashed, I had to reload the operating system to factory image. I named my computer exactly the same; but I'm wondering if some of the stuff in the volume table is causing a problem (ie: serialno, netname, etc??)
David
51
ThumbsPlus v7-v9 Questions / ThumbsPlus 7 : MySQL database : Part 1
« on: 2014-08-23 10:57:25 »
Folks,
I appreciate the replies so far. unfortunately, nothing has worked.
I'd like to ask for some information. if any of you have TP7 successfully installed with MySQL, could you please share the following??
(a) MYSQL version
(b) MYSQL ODBC connector version
(c) Workbench version
(d) copy of the SQL script you used to create the database.
thank you for the help
David
I appreciate the replies so far. unfortunately, nothing has worked.
I'd like to ask for some information. if any of you have TP7 successfully installed with MySQL, could you please share the following??
(a) MYSQL version
(b) MYSQL ODBC connector version
(c) Workbench version
(d) copy of the SQL script you used to create the database.
thank you for the help
David
52
ThumbsPlus v7-v9 Questions / ThumbsPlus 7 : MySQL database : Part 1
« on: 2014-08-17 17:58:37 »
Daan,
thank you again for the response. I've pasted below parts of the ODBC log (it's 290k characters and there's a 5000 character limit) that you suggested running a trace for. it's a lot of gobblygook; but maybe someone will understand parts of it.
best regards,
david
Thumbs 778-2b24 ENTER SQLAllocHandle
SQLSMALLINT 1
SQLHANDLE 0x00000000
SQLHANDLE * 0x030E061C
Thumbs 778-2b24 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1
SQLHANDLE 0x00000000
SQLHANDLE * 0x030E061C ( 0x03818638)
Thumbs 778-2b24 ENTER SQLSetEnvAttr
SQLHENV 0x03818638
SQLINTEGER 200
SQLPOINTER 3
SQLINTEGER 0
Thumbs 778-2b24 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x03818638
SQLINTEGER 200
SQLPOINTER 3
SQLINTEGER 0
Thumbs 778-2b24 ENTER SQLAllocHandle
SQLSMALLINT 2
SQLHANDLE 0x03818638
SQLHANDLE * 0x030E0620
Thumbs 778-2b24 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2
SQLHANDLE 0x03818638
SQLHANDLE * 0x030E0620 ( 0x038186B0)
Thumbs 778-2b24 ENTER SQLSetConnectAttr
SQLHDBC 0x038186B0
SQLINTEGER 103
SQLPOINTER 60
SQLINTEGER 0
Thumbs 778-2b24 EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x038186B0
SQLINTEGER 103
SQLPOINTER 60
SQLINTEGER 0
Thumbs 778-2b24 ENTER SQLSetConnectAttr
SQLHDBC 0x038186B0
SQLINTEGER 101
SQLPOINTER 0
SQLINTEGER 0
Thumbs 778-2b24 EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x038186B0
SQLINTEGER 101
SQLPOINTER 0
SQLINTEGER 0
Thumbs 778-2b24 ENTER SQLSetConnectAttr
SQLHDBC 0x038186B0
SQLINTEGER 108
SQLPOINTER 2
SQLINTEGER 0
Thumbs 778-2b24 EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x038186B0
SQLINTEGER 108
SQLPOINTER 2
SQLINTEGER 0
Thumbs 778-2b24 ENTER SQLDriverConnectW
HDBC 0x038186B0
HWND 0x00000000
WCHAR * 0x53378B34 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x53378B34
SWORD -3
SWORD * 0x00000000
UWORD 0
Thumbs 778-2b24 EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO)
HDBC 0x038186B0
HWND 0x00000000
WCHAR * 0x53378B34 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x53378B34 [-3]
SWORD -3
SWORD * 0x00000000
UWORD 0
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)
Thumbs 778-2b24 ENTER SQLAllocHandle
SQLSMALLINT 3
SQLHANDLE 0x038186B0
SQLHANDLE * 0x030E0648
Thumbs 778-2b24 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 3
SQLHANDLE 0x038186B0
SQLHANDLE * 0x030E0648 ( 0x013BF708)
Thumbs 778-2b24 ENTER SQLAllocHandle
SQLSMALLINT 3
SQLHANDLE 0x038186B0
SQLHANDLE * 0x030EAA08
Thumbs 778-2b24 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 3
SQLHANDLE 0x038186B0
SQLHANDLE * 0x030EAA08 ( 0x013BFA30)
thank you again for the response. I've pasted below parts of the ODBC log (it's 290k characters and there's a 5000 character limit) that you suggested running a trace for. it's a lot of gobblygook; but maybe someone will understand parts of it.
best regards,
david
Thumbs 778-2b24 ENTER SQLAllocHandle
SQLSMALLINT 1
SQLHANDLE 0x00000000
SQLHANDLE * 0x030E061C
Thumbs 778-2b24 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1
SQLHANDLE 0x00000000
SQLHANDLE * 0x030E061C ( 0x03818638)
Thumbs 778-2b24 ENTER SQLSetEnvAttr
SQLHENV 0x03818638
SQLINTEGER 200
SQLPOINTER 3
SQLINTEGER 0
Thumbs 778-2b24 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 0x03818638
SQLINTEGER 200
SQLPOINTER 3
SQLINTEGER 0
Thumbs 778-2b24 ENTER SQLAllocHandle
SQLSMALLINT 2
SQLHANDLE 0x03818638
SQLHANDLE * 0x030E0620
Thumbs 778-2b24 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2
SQLHANDLE 0x03818638
SQLHANDLE * 0x030E0620 ( 0x038186B0)
Thumbs 778-2b24 ENTER SQLSetConnectAttr
SQLHDBC 0x038186B0
SQLINTEGER 103
SQLPOINTER 60
SQLINTEGER 0
Thumbs 778-2b24 EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x038186B0
SQLINTEGER 103
SQLPOINTER 60
SQLINTEGER 0
Thumbs 778-2b24 ENTER SQLSetConnectAttr
SQLHDBC 0x038186B0
SQLINTEGER 101
SQLPOINTER 0
SQLINTEGER 0
Thumbs 778-2b24 EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x038186B0
SQLINTEGER 101
SQLPOINTER 0
SQLINTEGER 0
Thumbs 778-2b24 ENTER SQLSetConnectAttr
SQLHDBC 0x038186B0
SQLINTEGER 108
SQLPOINTER 2
SQLINTEGER 0
Thumbs 778-2b24 EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x038186B0
SQLINTEGER 108
SQLPOINTER 2
SQLINTEGER 0
Thumbs 778-2b24 ENTER SQLDriverConnectW
HDBC 0x038186B0
HWND 0x00000000
WCHAR * 0x53378B34 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x53378B34
SWORD -3
SWORD * 0x00000000
UWORD 0
Thumbs 778-2b24 EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO)
HDBC 0x038186B0
HWND 0x00000000
WCHAR * 0x53378B34 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x53378B34
SWORD -3
SWORD * 0x00000000
UWORD 0
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)
Thumbs 778-2b24 ENTER SQLAllocHandle
SQLSMALLINT 3
SQLHANDLE 0x038186B0
SQLHANDLE * 0x030E0648
Thumbs 778-2b24 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 3
SQLHANDLE 0x038186B0
SQLHANDLE * 0x030E0648 ( 0x013BF708)
Thumbs 778-2b24 ENTER SQLAllocHandle
SQLSMALLINT 3
SQLHANDLE 0x038186B0
SQLHANDLE * 0x030EAA08
Thumbs 778-2b24 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 3
SQLHANDLE 0x038186B0
SQLHANDLE * 0x030EAA08 ( 0x013BFA30)
53
ThumbsPlus v7-v9 Questions / ThumbsPlus 7 : MySQL database : Part 1
« on: 2014-08-17 16:15:35 »
Daan,
I thank you again for jumping in with some suggestions. unfortunately, none of those worked.
anyone else have any ideas?
is it possible that TP7 only works with an older version of the 32 bit ODBC driver I'm using???
I'm open to all suggestions.
best regards,
David
I thank you again for jumping in with some suggestions. unfortunately, none of those worked.
anyone else have any ideas?
is it possible that TP7 only works with an older version of the 32 bit ODBC driver I'm using???
I'm open to all suggestions.
best regards,
David
54
ThumbsPlus v7-v9 Questions / ThumbsPlus 7 : MySQL database : Part 2
« on: 2014-08-16 20:58:09 »
no question in this post. simply a follow up that copies the Chris Williams post from 2007 that I mentioned in my original post. truncated to 5000 characters.
===============================================================
group: cerious.advanced
Subject: T+ and MySQL - How It Works For Me
From: Chris Williams
Date: 5/21/2007 12:07PM
I have read several posts here about people struggling with T+ using
MySQL as a database. I have struggled too, but now have it working very
well and I thought I'd share my experience.
Caveat: I'm using Windows, with only the released versions of things --
no bleeding edge here. If you're using something else, YMMV (your
mileage may vary).
--- Versions
I found, like others, that the versions of the various pieces is
important. I'm using MySQL version 5.0.33, which I believe to be the
latest release version for Windows. The only version of the ODBC
connector I could get to work is the MySQL ODBC connector version 3.51.
All this is on top of T+ build 2234. This is what works for me.
--- Database
I used the excellent scripts posted in this message
<45e74987@phlipper.cerious.com> on March 1, 2007. Don't know who posted
them, but they work great. Whoever this is (the comments say "JPB"),
I'd like to know to thank them. I've been using the 5.16 version of the
database and it's fine.
As for the database format, I'm using InnoDB which works fine. To get
this to work in your MySQL config, you probably have to edit the my.cnf
file in the mysql/bin directory. Unfortunately Microsoft, in their
infinite wisdom has hardcoded the .cnf extension to some "speed dial"
program, and you can't open this file directly. If you double click on
it, or right click on it to edit it, nothing happens. Super... So what
I do is open an empty notepad window and drag this file into it. Then
you can edit it, save it, etc.
To get InnoDB to work you have to go down into the InnoDB part and
uncomment a bunch of things. First comment out "skip-innodb" by putting
a # in front of it. Then uncomment out all of the things with "=" in
them (all the "innodb_* = " and the "set-variable = " lines). You want
to set these locations and numbers to things that make sense. The
example my.cnf file has reasonable numbers to get started with.
Save your changes, restart MySQL, run the SQL scripts, and voila you
have a database. Install the ODBC connector driver, create an ODBC
connection and off you go.
--- Usernames
There was some discussion about whether or not you needed to create a
user for T+. I had used "root" for a while, but later switched to user
"ThumbsUser" with password "ThumbsUser" and this works for me. Just be
sure to make your ODBC connector match this.
--- "Not a Thumbs+ Database"
There has been a lot of discussion here about this error, and it bit me
three times. I rebuilt my entire T+ database (890,000 thumbs, thank
you) three times before I figured it out. What happens is that
magically you go along and one day T+ insists that the database you have
built, loved, and nurtured is not a T+ database. Panic ensues.
The problem is that T+ wants/needs the database to be in ANSI mode. The
script used to create it, sets ANSI mode on, and all seems fine. Until
you restart MySQL, and the default is for the SQL_MODE to be "". This
freaks out T+, and the database looks invalid.
The best solution for me was to put this:
sql_mode="ansi"
in the my.cnf file. I have it right after the InnoDB stuff (but before
the [mysqldump] section). This sets ANSI mode all the time. If you
want to see what mode you have, just put "select @@sql_mode;" in a query
window and press "go". By default you'll get a null return. With ANSI
mode on, you'll get something like:
REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ANSI
This is good, and will prevent the dreaded "not a Thumbs+ database".
--- "Database has gone away"
Several people have seen this error. It's particularly ugly because you
can't even close T+ without it getting this error repeatedly. Very ugly.
This is because the default MySQL wait timeout for a connection is
something like 28800 seconds (8 hours). If you leave T+ open longer
than that, it will time out, the connection will go away, life sucks.
The solution is to either a) exit and restart T+ more frequently than 8
hours, b) set a longer wait timeout, or c) both of the above. I have
set the wait timeout to 99999 (about 27.5 hours). I do this with this line:
wait_timeout=99999
in my my.cnf file (right after the sql_mode line). This works, and I
just shut down T+ every day. All is good.
--- Summary
I have been very successful getting T+ to work with MySQL, and am quite
happy. I offer this up as only my experience, and hope what I've
learned can help others.
Chris
=================================================================
===============================================================
group: cerious.advanced
Subject: T+ and MySQL - How It Works For Me
From: Chris Williams
Date: 5/21/2007 12:07PM
I have read several posts here about people struggling with T+ using
MySQL as a database. I have struggled too, but now have it working very
well and I thought I'd share my experience.
Caveat: I'm using Windows, with only the released versions of things --
no bleeding edge here. If you're using something else, YMMV (your
mileage may vary).
--- Versions
I found, like others, that the versions of the various pieces is
important. I'm using MySQL version 5.0.33, which I believe to be the
latest release version for Windows. The only version of the ODBC
connector I could get to work is the MySQL ODBC connector version 3.51.
All this is on top of T+ build 2234. This is what works for me.
--- Database
I used the excellent scripts posted in this message
<45e74987@phlipper.cerious.com> on March 1, 2007. Don't know who posted
them, but they work great. Whoever this is (the comments say "JPB"),
I'd like to know to thank them. I've been using the 5.16 version of the
database and it's fine.
As for the database format, I'm using InnoDB which works fine. To get
this to work in your MySQL config, you probably have to edit the my.cnf
file in the mysql/bin directory. Unfortunately Microsoft, in their
infinite wisdom has hardcoded the .cnf extension to some "speed dial"
program, and you can't open this file directly. If you double click on
it, or right click on it to edit it, nothing happens. Super... So what
I do is open an empty notepad window and drag this file into it. Then
you can edit it, save it, etc.
To get InnoDB to work you have to go down into the InnoDB part and
uncomment a bunch of things. First comment out "skip-innodb" by putting
a # in front of it. Then uncomment out all of the things with "=" in
them (all the "innodb_* = " and the "set-variable = " lines). You want
to set these locations and numbers to things that make sense. The
example my.cnf file has reasonable numbers to get started with.
Save your changes, restart MySQL, run the SQL scripts, and voila you
have a database. Install the ODBC connector driver, create an ODBC
connection and off you go.
--- Usernames
There was some discussion about whether or not you needed to create a
user for T+. I had used "root" for a while, but later switched to user
"ThumbsUser" with password "ThumbsUser" and this works for me. Just be
sure to make your ODBC connector match this.
--- "Not a Thumbs+ Database"
There has been a lot of discussion here about this error, and it bit me
three times. I rebuilt my entire T+ database (890,000 thumbs, thank
you) three times before I figured it out. What happens is that
magically you go along and one day T+ insists that the database you have
built, loved, and nurtured is not a T+ database. Panic ensues.
The problem is that T+ wants/needs the database to be in ANSI mode. The
script used to create it, sets ANSI mode on, and all seems fine. Until
you restart MySQL, and the default is for the SQL_MODE to be "". This
freaks out T+, and the database looks invalid.
The best solution for me was to put this:
sql_mode="ansi"
in the my.cnf file. I have it right after the InnoDB stuff (but before
the [mysqldump] section). This sets ANSI mode all the time. If you
want to see what mode you have, just put "select @@sql_mode;" in a query
window and press "go". By default you'll get a null return. With ANSI
mode on, you'll get something like:
REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ANSI
This is good, and will prevent the dreaded "not a Thumbs+ database".
--- "Database has gone away"
Several people have seen this error. It's particularly ugly because you
can't even close T+ without it getting this error repeatedly. Very ugly.
This is because the default MySQL wait timeout for a connection is
something like 28800 seconds (8 hours). If you leave T+ open longer
than that, it will time out, the connection will go away, life sucks.
The solution is to either a) exit and restart T+ more frequently than 8
hours, b) set a longer wait timeout, or c) both of the above. I have
set the wait timeout to 99999 (about 27.5 hours). I do this with this line:
wait_timeout=99999
in my my.cnf file (right after the sql_mode line). This works, and I
just shut down T+ every day. All is good.
--- Summary
I have been very successful getting T+ to work with MySQL, and am quite
happy. I offer this up as only my experience, and hope what I've
learned can help others.
Chris
=================================================================
55
ThumbsPlus v7-v9 Questions / ThumbsPlus 7 : MySQL database : Part 1
« on: 2014-08-16 20:55:56 »
hello all,
well - as luck would have it, my computer crashed in a recent thunder storm. I've been busily reloading all my software for the past few days. I've now gotten around to the difficult stuff. I consider TP7 difficult. before the crash, I had successfully created a MySQL db for TP7 and was using TP7 Pro sp2; having been reluctant to move to either TP8 or TP9 based on forum comments.
well, up to this point, I've not been able to successfully get TP7 to work again with MySQL. I hope to get some assistance on this forum. Here's what I've done so far. I've gone from memory as well as making use of a very old post from the Cerious Archives by Chris Williams. I've gone ahead and posted this in it's entirety at the bottom of my post for other folks reference -as I've found it quite helpful in reconstructing TP7 with MySQL.
I'm running Win7 Home Premium 64 bit sp1 with 8gig memory
so, here's what I've done so far.
(a) installed MySQL Community Server v5.6.2 (not sure if relevant; but before my crash, I was using an older version)
(b) installed Workbench v6.1 (not sure if relevant; but before my crash, I was using an older version)
(c) ensured MySQL service is running
(d) restored my backup dump files for my ThumbsPlus db in Workbench (yep, I had a backup). I can connect to the Thumbs db in Workbench and I can see the tables in Workbench as well. My data looks fine.
(e) installed 32 bit ODBC. yep, somehow I managed to remember that TP7 is 32 bit and since I'm running Win7 64 bit, I had to install ODBC 32 bit for TP7 to see the ODBC data source.
(f) created the ThumbsPlus ODBC data source in the 32 bit ODBC.
(g) ensured that I have appropriate permissions to the schema within Workbench.
(h) changed the SQL_mode to 'ANSI' in the my.ini file.
(i) verified in Workbench that SQL_mode is set to 'ANSI'. It is.
(j) run TP7. choose "file / database / connect / machine data source/ thumbs
(k) get the following error message :<)
does anyone have any thoughts on what the problem is here?? I'd sure love to be able to get back to where I was before my laptop crashed.
thank you in advance for any help provided.
because of the 5000 character post limitation, I need to put the 5/21/2007 post from Chris Williams in a 2nd post. sorry about that.
well - as luck would have it, my computer crashed in a recent thunder storm. I've been busily reloading all my software for the past few days. I've now gotten around to the difficult stuff. I consider TP7 difficult. before the crash, I had successfully created a MySQL db for TP7 and was using TP7 Pro sp2; having been reluctant to move to either TP8 or TP9 based on forum comments.
well, up to this point, I've not been able to successfully get TP7 to work again with MySQL. I hope to get some assistance on this forum. Here's what I've done so far. I've gone from memory as well as making use of a very old post from the Cerious Archives by Chris Williams. I've gone ahead and posted this in it's entirety at the bottom of my post for other folks reference -as I've found it quite helpful in reconstructing TP7 with MySQL.
I'm running Win7 Home Premium 64 bit sp1 with 8gig memory
so, here's what I've done so far.
(a) installed MySQL Community Server v5.6.2 (not sure if relevant; but before my crash, I was using an older version)
(b) installed Workbench v6.1 (not sure if relevant; but before my crash, I was using an older version)
(c) ensured MySQL service is running
(d) restored my backup dump files for my ThumbsPlus db in Workbench (yep, I had a backup). I can connect to the Thumbs db in Workbench and I can see the tables in Workbench as well. My data looks fine.
(e) installed 32 bit ODBC. yep, somehow I managed to remember that TP7 is 32 bit and since I'm running Win7 64 bit, I had to install ODBC 32 bit for TP7 to see the ODBC data source.
(f) created the ThumbsPlus ODBC data source in the 32 bit ODBC.
(g) ensured that I have appropriate permissions to the schema within Workbench.
(h) changed the SQL_mode to 'ANSI' in the my.ini file.
(i) verified in Workbench that SQL_mode is set to 'ANSI'. It is.
(j) run TP7. choose "file / database / connect / machine data source/ thumbs
(k) get the following error message :<)
does anyone have any thoughts on what the problem is here?? I'd sure love to be able to get back to where I was before my laptop crashed.
thank you in advance for any help provided.
because of the 5000 character post limitation, I need to put the 5/21/2007 post from Chris Williams in a 2nd post. sorry about that.
56
ThumbsPlus v7-v9 Questions / ThumbsPlus 7 (+ older) tech support newsgroup archives
« on: 2014-08-16 20:36:23 »
Daan,
ever since I started taking a look at these forums; I've seen you always be willing to offer helpful responses. thank you so much for the quick response. I've downloaded agent and am happily importing all the old Cerious newsgroup .txt files that you so kindly provided.
best regards,
David
ever since I started taking a look at these forums; I've seen you always be willing to offer helpful responses. thank you so much for the quick response. I've downloaded agent and am happily importing all the old Cerious newsgroup .txt files that you so kindly provided.
best regards,
David
57
ThumbsPlus v7-v9 Questions / ThumbsPlus 7 (+ older) tech support newsgroup archives
« on: 2014-08-16 14:11:13 »
hello,
has anyone managed to import these raw text files into a newsreader with success? it'd be much easier to use than searching through the raw text files. if so, what newsreader? I'm having a difficult time finding an open source newsreader these days.
thank you
has anyone managed to import these raw text files into a newsreader with success? it'd be much easier to use than searching through the raw text files. if so, what newsreader? I'm having a difficult time finding an open source newsreader these days.
thank you
58
ThumbsPlus v7-v9 Questions / How Long Does It Take Cerious To Respond? (Need Reg Code)
« on: 2012-04-07 19:46:14 »
it's a good product, so folks have patience. it's also apparently a small company, which lots of folks like to support - including myself. that said. I've had a couple questions outstanding for a few months now without response. this is not a new issue, it's been the case for quite some time now. anyway, just my 2 cents.
59
ThumbsPlus v7-v9 Questions / How Long Does It Take Cerious To Respond? (Need Reg Code)
« on: 2012-04-04 21:36:01 »
hello,
>> Does it normally take them awhile to respond?
in answer to this specific question - Cerious will never respond. many folks on this forum have had outstanding support requests out to Cerious that simply are never answered. I'm one of them.....
>> Does it normally take them awhile to respond?
in answer to this specific question - Cerious will never respond. many folks on this forum have had outstanding support requests out to Cerious that simply are never answered. I'm one of them.....