Uh, I specifically said I had not used such some of the options but had used varchar and find that it works in all the cases I have used. If there is going to be truncation the DB will inform and the query will fail. I only gave advice on using varchar for text fields.
Ray Thompson Tau Beta Pi - www.tbp.org The Engineering Honor Society 865-546-4578 > -----Original Message----- > From: Peter Boughton [mailto:[email protected]] > Sent: Wednesday, March 10, 2010 12:44 PM > To: sql > Subject: Re: cfqueryparam and MySQL text field > > > > I don't know what CLOB is as I have never used it. LongVarChar I have > also not > > used. I do know that varchar will probably work just fine. > > :/ If I'm not sure what things are, I tend to RTFM before advising > one way or the other. > > In MySQL, varchar columns cannot hold more than 65536 bytes per row, > which is why longvarchar/clob data types exist - to hold larger > amounts of text data. > > I don't know whether the cfsqltype takes these limits into account, > which is why it's better to use the cfsqltype which corresponds to the > actual database type, in case there is some odd side-effect or > truncation. > > > Also, whilst we're on the subject: > Make sure your Datasource settings are not artificially > limiting/truncating your clob/blob fields in the advanced setting. > If you rename a datasource, these values can get reset! > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/sql/message.cfm/messageid:3304 Subscription: http://www.houseoffusion.com/groups/sql/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/sql/unsubscribe.cfm
