On Tue, 25 Mar 2014, Dennis Poon wrote:
By the way, why isn't a semicolon required at the end of SET NAMES 'utf8'
command? I tried both with and without semicolon and neither raise an
error.
Seems, that MySQL is tolerant to this.
MySQL supports MULTI_STATEMENTS, which enables client to p
On Tue, March 25, 2014 09:56, Dennis Poon wrote:
>
>>>
>>> By the way, why isn't a semicolon required at the end of SET NAMES
>>> 'utf8' command? I tried both with and without semicolon and neither
>>> raise an error.
>> Seems, that MySQL is tolerant to this.
>> MySQL supports MULTI_STATEMENTS, whi
By the way, why isn't a semicolon required at the end of SET NAMES
'utf8' command? I tried both with and without semicolon and neither
raise an error.
Seems, that MySQL is tolerant to this.
MySQL supports MULTI_STATEMENTS, which enables client to pass multiple
statements separated by ";" in
Dennis Poon wrote / napísal(a):
LacaK wrote:
Dennis Poon wrote / napísal(a):
I tried, the results are:
@@character_set_client : utf8
@@character_set_connection : latin1
@@character_set_database : latin1
Dennis, do you received my reply?:
IMO @@character_set_connection is wron
LacaK wrote:
Dennis Poon wrote / napísal(a):
I tried, the results are:
@@character_set_client : utf8
@@character_set_connection : latin1
@@character_set_database : latin1
Dennis, do you received my reply?:
IMO @@character_set_connection is wrong and must be utf8.
I will try fix
Dennis Poon wrote / napísal(a):
I tried, the results are:
@@character_set_client : utf8
@@character_set_connection : latin1
@@character_set_database : latin1
Dennis, do you received my reply?:
IMO @@character_set_connection is wrong and must be utf8.
I will try fix it, but first c
I tried, the results are:
@@character_set_client : utf8
@@character_set_connection : latin1
@@character_set_database : latin1
Dennis, do you received my reply?:
IMO @@character_set_connection is wrong and must be utf8.
I will try fix it, but first can you try as workaround this:
- a
Dennis Poon wrote / napísal(a):
I tried, the results are:
@@character_set_client : utf8
@@character_set_connection : latin1
@@character_set_database : latin1
Dennis, do you received my reply?:
IMO @@character_set_connection is wrong and must be utf8.
I will try fix it, but fir
LacaK wrote:
Dennis Poon wrote / napísal(a):
Dennis Poon wrote:
Michael Van Canneyt wrote:
On Fri, 14 Mar 2014, Dennis Poon wrote:
the content appeared as garbage.
I already specified the CHARSET=utf8 in the Create Table SQL.
Did you set the TSQLConnection.Charset property to UT
Dennis Poon wrote / napísal(a):
Dennis Poon wrote:
Michael Van Canneyt wrote:
On Fri, 14 Mar 2014, Dennis Poon wrote:
the content appeared as garbage.
I already specified the CHARSET=utf8 in the Create Table SQL.
Did you set the TSQLConnection.Charset property to UTF8 as well ?
Dennis Poon wrote / napísal(a):
Dennis Poon wrote:
Michael Van Canneyt wrote:
On Fri, 14 Mar 2014, Dennis Poon wrote:
the content appeared as garbage.
I already specified the CHARSET=utf8 in the Create Table SQL.
Did you set the TSQLConnection.Charset property to UTF8 as well ?
Dennis Poon wrote:
Michael Van Canneyt wrote:
On Fri, 14 Mar 2014, Dennis Poon wrote:
the content appeared as garbage.
I already specified the CHARSET=utf8 in the Create Table SQL.
Did you set the TSQLConnection.Charset property to UTF8 as well ?
I set it to utf8 (UTF-8 will raise
Michael Van Canneyt wrote:
On Fri, 14 Mar 2014, Dennis Poon wrote:
the content appeared as garbage.
I already specified the CHARSET=utf8 in the Create Table SQL.
Did you set the TSQLConnection.Charset property to UTF8 as well ?
I set it to utf8 (UTF-8 will raise exception) but still
On Fri, 14 Mar 2014, Dennis Poon wrote:
Is TSQLQuery.AppleUpdate works with UTF8 string field content?
I fetched a web page and extracted part of its content and appended it into
TSQLQuery record's string field.
The web page content is Chinese in UTF-8 encoding.
I 'writeln' the content be
14 matches
Mail list logo
