Are there any plans to add support for mapping SQL_SS_TIMESTAMPOFFSET to/from TIMESTAMP WITH TIME ZONE in the SQL Anywhere ODBC drivers? The MobiLink server .NET API reference says that they "can be used only against Microsoft SQL Server and Oracle databases".
If not, could encouragement from users spark interest? Is there a technical issue that flat out prevents it? Is it (fingers crossed) actually supported, but just not documented?
After all, the documentation (Ways to send dates and times to the database) says "The date and time of day with a time zone offset can be sent to the database as a string only.", but I've found that Entity Framework, at least, happily maps TIMESTAMP WITH TIME ZONE to System.DateTimeOffset.
asked 28 May '13, 21:05
Yes there is - maybe not "prevent" it from ever happening, but certainly "makes it more difficult to implement". In general, our ODBC driver targets ODBC version 3.5, due to general compatibility concerns with third-party ODBC driver managers on UNIX operating systems (e.g. unixODBC, and iODBC). From: http://msdn.microsoft.com/en-us/library/bb677267.aspx
So we would have to re-target our ODBC compliance level for our ODBC driver and then third-party ODBC managers have to implement ODBC 3.8, in order to make such a change fully work.
This is a string to native type mapping that happens inside the provider. It's still returned as a string back from the database underneath the covers.
Is there a specific issue are you encountering due to this issue? Most of our customers are able to use the TIMESTAMP WITH TIME ZONE type directly as a string.