Re: [Quickfix-users] Sql Server ODBC issues

[Oren M. <or...@qu...>]

> You might consider using the fully qualified table names in case
someone=20
> like me runs into this ODBC connection issue in the future. I think it=20
> is good practice to use fully qualified names for db objects in
general=20
> isnt it?

We don't fully qualify because some people may not want to use a
database called quickfix.  If someone puts the tables in the default
context, then that may very well be their intention.  The main issue is
that we are crashing instead of providing a proper ConfigException.
This was due to a ConfigError pointer being thrown instead of a
reference.  This has been fixed and QuickFIX will now report a
connection problem in this case (due to being unable to populate the
cache).

> There are a couple of other issues too:
>=20
> -From time to time the trace log shows that inserts into messages_log=20
> are failing because a NULL is being inserted in the SESSION_QUALIFIER=20
> column, which is defined as NOT NULL in the sql create script.

This column should be nullable.  We will fix it.

> - The columns MESSAGES_LOG.TEXT and MESSAGES.MESSAGE are, at least in
my=20
> database, being truncated - only the section of the text "8=3DFIX.4.4"=20
> exists. I see that the sql string is being built with a lot of=20
> backslashes - is that some kind of MYSQL escape char that MSSQL is not=20
> enjoying?

I believe this is a result of MSSQL tools interpreting the SOH character
as some sort of end of string.  The correct values are actually in
there.

-oren