I've had to use the same method that Trevor mentions below and it has always worked on 5.0. I've yet to upgrade to 5.5 so I can't comment on whether or not it works for me, but now I'm worried about it.
Trevor, please raise this as a bug with Witango if you can easily reproduce it.
/John
Ben Johansen wrote:
Can you explain why you need the quotes when it is a char field?
Have you tried the noSQLEncoding switch
Around the update action
Ben
------------------------------------------------------------------------
*From:* Trevor Green [mailto:[EMAIL PROTECTED] *Sent:* Friday, October 15, 2004 6:20 PM *To:* [EMAIL PROTECTED] *Subject:* Witango-Talk: problem with quote value and 5.5 server
I have a problem with 5.5 on Mac OSX server and MySql. I have an update action with a field which is has the Quote value attribute set to false. I am trying to update the field with the following expression
<@ifempty <@arg ownership>>null<@else>'1'</@if>
i.e. sql should read /field=null/ or /field=’1’/ depending on the value of ownership. This worked fine on 5.0 but since upgrading to 5.5 the server insists on quoting even when quote value is set to false. So, I either get a value of null (i.e. the word null being stored in the field – which is a char field) or the value ‘1’ (i.e. quote 1 quote) instead of having an empty field or a field with the value of 1. Has anyone else experienced this?
Trevor Green
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
