Comments on: Using Macro Scheduler’s Database Functions

By: Marcus Tettmar

Marcus Tettmar — Thu, 05 Nov 2009 15:43:01 +0000

That would be done with the connection string and would be database specific. For MySQL, according to this site, you would add "CharSet=UTF8" to the connection string. It may be different (or unnecessary) for other databases. Refer to the documentation for the database in question.

By: Emanuel

Emanuel — Thu, 05 Nov 2009 14:30:36 +0000

Is there an possibility to choose the charset? Like in PHP (to mysql)
mysql_set_charset(’utf8′,$link);

Would like to store swedish characters å,ä,ö,Å,Ä,Ö

Regards Emanuel

By: raphael

raphael — Wed, 14 Oct 2009 11:42:39 +0000

Per the mysql reference (http://dev.mysql.com/doc/refman/5.0/en/string-syntax.html), your second example works. Thanks.

By: Marcus Tettmar

Marcus Tettmar — Mon, 12 Oct 2009 08:47:05 +0000

This may depend on the database, but if you’re using single quotes around the item then I don’t think you need to escape the double quote. If you’re using double quotes around the item then you just use two double quotes where you need to insert a double quote. I.e.:

Let>SQL=INSERT INTO sometable VALUES (10, ‘“‘ );

Or:

Let>SQL=INSERT INTO sometable VALUES (10, ““”” );

However, the backslash thing is probably database specific so it may depend on your database and what kind of connection string you are using. As far as I am aware ADO itself doesn’t need the double quote escaped unless you’re using the double quote as the string delimiter in which case you just add an extra double quote as above (just like in VBScript).

By: raphael

raphael — Sun, 11 Oct 2009 00:40:27 +0000

Not a comment, but apropos: I’m trying to use DBExec to insert a string containing a double quote into a mysql mediumtext field via ODBC. Normally, you’d do this by simply escaping the double quote with a backslash in the insert statement. For example:

Let>SQL=INSERT INTO sometable VALUES (10, ‘\”‘ );
DBExec>dbH,SQL,result

Where dbH is a working db connection. I get a zero result when I run this. How are you processing escape characters? What facilities exist to dive deeper into the error? Nothing’s coming through in the mysql error and query logs.