Dev Studio can see MySQL database now on server. Just a matter of installing the right iODBC manager and drivers per Jason's instructions. By running with just a system DSN on my workstation, I can see the datasources on the server in the dev studio. Therefore I can create a taf.
On server, I went through same routine: installing mysql, iodbc, and drivers and creating a server datasource.
It didn't fly. I get:
File: testnewrecord.taf
Position: Insert
Class: DBMS
Main Error Number: 1049
[MySQL][ODBC 3.51 Driver]Unknown database 'mysqltest2'
HY000
The terminal shows: Unable to open to odbc.mysqltest2 due to an error during connection
going back a few hundred times to make sure I had it right, it still says that.
Installed latest version of witango server and rebooted
same error.
looks like odbc driver can't see or process the DSN.
Jason was stumped and ran for his sailboat to get some salt air in his brain.
I'm high and dry.
Been poking at everything and it's not budging.
- tweaking taf: having dev and deployment same, making them separate, etc., changing user
- tweaking DSN on local machine this way and that
- deleting and re-entering DSN on server, modifying 'server' value from localhost to 127.0.0.1 to the IP of the machine..
- creating a new test db in mysql, etc.
How come the dev studio can see the databases but the server can't??
On Friday, July 11, 2003, at 11:14 AM, Steve Smith wrote:
First, you don't need both a user and a system DSN and this may be the cause of your problems. Second, I looked over my system and there is a configuration file ODBC for the Dev Studio. It is found in Witango/Dev Studio 5.0/Configuration/ and is called ODBCConfig.plist. Mine contains the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist SYSTEM "file://localhost/System/Library/DTDs/PropertyList.dtd">
<plist version="0.9">
<dict>
<key>managername</key>
<string>iODBC</string>
<key>managertype</key>
<string>dyld</string>
<key>corename</key>
<string>iODBC.framework</string>
<key>corepath</key>
<string>/Library/Frameworks</string>
<key>configname</key>
<string>iODBCinst.framework</string>
<key>configpath</key>
<string>/Library/Frameworks</string>
</dict>
</plist>
I'm not sure if this could be the cause of your problems or not but my guess is that it is. I just tried moving it to the desktop and then I started the Dev Studio, My ODBC data sources were missing. I quit the Dev Studio, moved the ODBCConfig.plist back into the Configuration file and my data sources returned.
Sorry that I didn't think of that earlier.
Hope this helps,
Steve Smith
Oakbridge Information Solutions
Office: (519) 624-4388
GTA: (416) 606-3885
Fax: (519) 624-3353
Cell: (416) 606-3885
Email: [EMAIL PROTECTED]
Web: http://www.oakbridge.ca
On Thursday, July 10, 2003, at 06:37 PM, Roland Dumas wrote:
So if I use the default MySQL setup, there is a 'test' database. I create a table with a few fields in it so there is something to play with.
then I get out the ODBC manager and create a user and a system DSN, having entered in the information about the driver.
Then, the next time I open the dev studio, it should just appear in the ODBC data sources? Is there some other incantation I need to do, because this doesn't work.
This is just on the local machine. Haven't gotten to the server yet.
On Wednesday, July 9, 2003, at 01:29 PM, Steve Smith wrote:
Unfortunately, as has been the case on the Mac platform for a number of years now (since Visigenic ODBC Driver Manager was available) you CANNOT create ODBC data sources from within the Dev Studio. If you have the Dev Studio open, then go to your ODBC Manager (such as iODBC or myodbc) to create and/or modify a data source, you need to close the Dev Studio and reopen it to see the data source changes.
I've been running ODBC datasources between Witango and MySQL successfully for a few months now. I use iODBC and have had better success with it. I did make an attempt to use myodbc but couldn't get it to work correctly.
Set your data source up as a system data source. Select the 'Add' button and the correct driver, then set up your data source by adding keywords for:
server
database
user
password
where 'server' = either 'localhost' or the ip address of the machine running MySQL. Database is the name of the mysql database, user is the name of a user who has access privileges and rights to the database, and the password associated with that user.
You shouldn't have to create any new files.
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
