Looks like a reasonable change to me. I'll run some tests on it and merge it in over the weekend unless Doug beats me to it...
On 4/7/06, Daryl <[EMAIL PROTECTED]> wrote: > I made the following change to ObjectDao.cfc to get up and running > with CF Reactor on this particular MySQL4 database: > > I added the problem datatypes to the numeric case in this function > (line 238 in the current ObjectDao.cfc in the /reactor/data/mysql4 > folder: > i.e., i appended "bigint unsigned,smallint unsigned,mediumint > unsigned" to the relevant case: > > <cffunction name="getCfDataType" access="private" hint="I translate > the MSSQL data type names into ColdFusion data type names" > output="false" returntype="string"> > <cfargument name="typeName" hint="I am the type name to > translate" > required="yes" type="string" /> > > <cfswitch expression="#arguments.typeName#"> > <cfcase value="bit,bool,boolean"> > <cfreturn "boolean" /> > </cfcase> > <cfcase > value="tinyint,smallint,mediumint,int,integer,bigint,float,double,double > percision,decimal,dec,year,bigint unsigned,smallint unsigned,mediumint > unsigned"> > <cfreturn "numeric" /> > </cfcase> > <cfcase value="date,datetime,timestamp"> > <cfreturn "date" /> > </cfcase> > <cfcase value="time,enum,set"> > <cfreturn "string" /> > </cfcase> > <cfcase > value="char,varchar,tinytext,text,mediumtext,longtext"> > <cfreturn "string" /> > </cfcase> > <cfcase > value="binary,varbinary,tinyblob,blob,mediumblob,longblob"> > <cfreturn "binary" /> > </cfcase> > </cfswitch> > > <cfthrow message="Unsupported (or incorrectly supported) > database > datatype: #arguments.typeName#." /> > > </cffunction> > > That worked in terms of being able to get up and running with querying > data using reactor. I only > started working with this last night and do not know if that change > will work in terms of > table relations/everything else. -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/

