Ole Willy Tuv wrote:

> << Apart from the new binary constant support in 1.03, yes. >>
>
> X'476F6F64206E65777321'
>
> Ole Willy Tuv

My brain hurts,,,,

--

X'416772656564203C673E'

X'42696C6C'

><< Apart from the new binary constant support in 1.03, yes. >>
>
>X'476F6F64206E65777321'
>
>Ole Willy Tuv
>

X'446F6E277420796F75206D65616E20612068657820656469746F723F'

><< Uh! >>
>
>X'4E6F7720796F75206E6565642061206865782065646974696F7221'
>
>Ole Willy Tuv
>

Tim,

The binary constant support is good news.  A question though... as you
can see, we have been entering some constants in the messages using
the X'nnnn'  format.  Everything I have found says that the format
should be:  "Binary constants have the prefix 0x and are a string of
hexadecimal numbers. They are not enclosed in quotation marks"

Here is one reference:
http://msdn2.microsoft.com/en-us/library/ms179899.aspx

Are you planning to implement the 0x prefix method or the X'nnn'
method?  Personally, I prefer the 0x prefix method.


0x2D2042696C6C


>Roy,
>
><< As always with OLH once you know where to look its obvious I presume
>these are the only types needing a prefix? >>
>
>Apart from the new binary constant support in 1.03, yes.

Bill,

<< X'446F6E277420796F75206D65616E20612068657820656469746F723F' >>

Yes, sorry for the typo

Ole Willy Tuv

Bill,

<< Everything I have found says that the format should be:  "Binary
constants have the prefix 0x and are a string of hexadecimal numbers. They
are not enclosed in quotation marks" >>

I think that's a proprietary Transact-SQL syntax. The X'nnnn' format is the
standard SQL syntax:

<binary string literal> ::=
   X <quote> [ { <hexit> <hexit> }... ] <quote>

Ole Willy Tuv

Hmm, I don't have the SQL 2003 syntax or specifications and I knew
that the site I referred to was for Transact SQL but other pages I
found also spoke about the 0xnnn specification and they were referring
specifically to the SQL:2003 standards, not Transact SQL.

Since *true* constant binary notation is really along the lines of
B'010101101010', I figured the X'.....' notation was the actual spec
but was sure hoping for the 0x.... standard.

Not that Delphi really cares, and its not hard to do, but building a
Delphi string with embedded single quotes is a bit ugly, but so are
many other things.

>Bill,
>
><< Everything I have found says that the format should be:  "Binary
>constants have the prefix 0x and are a string of hexadecimal numbers. They
>are not enclosed in quotation marks" >>
>
>I think that's a proprietary Transact-SQL syntax. The X'nnnn' format is the
>standard SQL syntax:
>
><binary string literal> ::=
>    X <quote> [ { <hexit> <hexit> }... ] <quote>
>
>Ole Willy Tuv
>

Bill,

<< Hmm, I don't have the SQL 2003 syntax or specifications and I knewthat
the site I referred to was for Transact SQL but other pages I found also
spoke about the 0xnnn specification and they were referringspecifically to
the SQL:2003 standards, not Transact SQL. >>

The X'' format is the SQL 2003 standard.

<< Not that Delphi really cares, and its not hard to do, but building a
Delphi string with embedded single quotes is a bit ugly, but so are many
other things. >>

We've got a TEDBEngine.BinaryToSQLStr method along with a
TEDBEngine.QuotedSQLStr method to handle this for you.  All you have to do
is add the X at the beginning.

http://www.elevatesoft.com/edb1d7_tedbengine_binarytosqlstr.htm
http://www.elevatesoft.com/edb1d7_tedbengine_quotedsqlstr.htm

--
Tim Young
Elevate Software
www.elevatesoft.com