A little off topic maybe, but I found that some of the connection errors can be solved with using the old_password() function in mysql.
I don't really know which version of the mysql client FME uses, but it seems that pre 4.1 clients use a short hash for the passwords where later version are able to handle a longer hash. This problem can be solved by changing your password for the user using the old_password() function in mysql. For more information on this function and how to use it check: http://dev.mysql.com/doc/refman/5.0/en/old-client.html This solved a lot of problems for me with FME and MySQL (both spatial and non-spatial). Kind regards, Klaas Ardinois ---------------- Klaas Ardinois Ontrack Navigation IT Manager Biebuycklaan 28 9050 Gentbrugge - Belgium ---------------- -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of wallace_tobin Sent: woensdag 19 april 2006 0:13 To: [email protected] Subject: [fme] Re: MYSQL licensing requirements? --- In [email protected], "mark2atsafe" <[EMAIL PROTECTED]> wrote: > > Have a look through http://www.safe.com/reader_writerPDF/mysql.pdf to > see if there is anything in there relating to the settings that will > help. There is a great troubleshooting section for connecting to MySQL. > > > In theory I think FME is only certified to work with the paid version > of MySQL, not the free download. I'm 90% sure that this isn't the > problem here, but thought I'd mention it anyway. > > Failing this can you write non-spatial data? Or does it produce the > same message? > > Hope this helps. > > Mark > > Mark Ireland, Product Support Engineer > Safe Software Inc. Surrey, BC, CANADA > [EMAIL PROTECTED] http://www.safe.com > Solutions for Spatial Data Translation, Distribution and Access > > --- In [email protected], "wallace_tobin" <wtobin@> wrote: > > > > --- In [email protected], Hans van der Maarel <hans@> wrote: > > > > > > wallace_tobin wrote: > > > > I am using a free download of MYSQL 5.0.18 which is supposed to > > > > support Geometric data types. I'm able to create the geometry > > column > > > > within the MySQL table as well as a spatial index for it however > > when > > > > I attempt to populate the table using FME I keep getting an error > > on > > > > the following: > > > > > > > > Error executing SQL query ('CREATE TABLE `root.ATSQTRS` > > (`ATSQTRID` > > > > int PRIMARY KEY,`MER` int,`QTR` char(2),`QTRID` int,`RGE` > > int,`SEC` > > > > int,`TWP` int,`TWPID` int,`QTRSHAPE` GEOMETRY) > > > > ENGINE=MYISAM'): 'Incorrect table name 'root.ATSQTRS''. > > > > Successfully closed MYSQL database writer. > > > > Writer failed in open() call. > > > > Writer failed in open() call. > > > > > > > > Is this due to a licensing problem? Do I require a specfic MySQL > > FME > > > > extension to get this to work? All that I am doing is mapping > > the > > > > contents of a shape file into FME and storing a polygon shape > > into > > > > the geometry column of the MySQL table. Can someone point me in > > the > > > > right direction for help on using this feature. > > > > > > I never had any trouble using the MySQL reader/writer. If it shows > > up in > > > your formats list, you have the correct FME version for it. > > > > > > Check the properties of the MySQL output feature, there should be > > an > > > option there that says "Table Exists". Based on what you're > > writing, it > > > sounds as if you have already created the table and then FME tries > > to do > > > that as well. > > > > > > Hope this helps... > > > -- > > > Hans van der Maarel > > > Red Geographics > > > www.redgeographics.com / hans@ > > > > > Yes Hans. I have already created the table I don't see and option > > within FME to select "Table Exists". In fact it was something I had > > expected to be able to choose. The root user has ull priveleges on > > the database. The interesting thing here is that it is trying to > > create the table root.ATSQTRS when in fact the database name > > is 'UGS_Database_be'. I supplied 'root' as the database user. Maybe > > I'm not supllying the information correctly? > > > The problem seems to lie in the syntax of the Create Table statement. FME generated it as `ugs_database_be.atsqtrs` when it should be `ugs_database_be`.`atsqtrs`. Maybe this is a MySQL version issue? I changed the name of the table I am trying to write to (`atsqtrs) and changed the database user to the name of the database I'm attempting to write to (ugs_database_be`). This set up the proper syntax for the create table statement that fme runs automatically if it doesn't find the table. The thing is I had to remove the table in order to get this to run and let FME add it itself. Still never found the option to tell fme that the MySQL "table exists". I guess it checks for it first and then goes on if it finds it, otherwise it creates the table. After getting by the first problem I am then hit with the following insert error: Error was 'Out of range value adjusted for column 'ATSQTRID' at row 1'. The field length for this column was INT (11) while the field value being inserted was a 10 digit integer. Not sure why this fails but this error may not even be related to that field anyway. Mark, maybe you're right about the free version not having this option included. It looks like the MySQL features within FME are only guaranteed to work with MySQL Network. I'll have to look into what features it supplies and make the decision to get it. Thanks for your help Hans and Mike. Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
