In your excellent documentation here you make reference to an integer code for SQL 'datetimeoffset' (ie. -155). I have looked and not found a single reference that can give me that or any of the other codes. Could you provide a reference?

Thanks for that documentation btw. Saved me a lot of time!

本篇文章内容引导，如何在 asp.net core 项目中使用特性(注解) 的方式管理事务。

UnitOfWorkManager 只可以管理 Repository 仓储对象的事务，直接 fsql.Insert<T>() 是不行的！！

支持六种传播方式(propagation)，意味着跨方法的事务非常方便，并且支持同步异步：

• Requierd：如果当前没有事务，就新建一个事务，如果已存在一个事务中，加入到这个事务中，默认的选择。
• Supports：支持当前事务，如果没有当前事务，就以非事务方法执行。
• Mandatory：使用当前事务，如果没有当前事务，就抛出异常。
• NotSupported：以非事务方式执行操作，如果当前存在事务，就把当前事务挂起。
• Never：以非事务方式执行操作，如果当前事务存在则抛出异常。
• Nested：以嵌套事

I need Some Hellp about instruction how to use SOCI from cmake as subporject "add_subdirectory(SOCI)"
I have long time try use It but SOCI::* not work. I know this about CMake but no one try to help. And How I can do in way from SOCI CMake script Variables. How I can do that ?

Could you please add some information in the docs whether turbodbc support SQLite or not?
Is it fast or slow?

There doesn't seem to be a single mention of "sqlite" in the docs currently:
https://turbodbc.readthedocs.io/en/latest/search.html?q=sqlite&check_keywords=yes&area=default

My current use case is that I have ~ 10 pandas Dataframes, each ~ 100 MB in size, and would like to write the

Connecting to Azure SQL database using access token via pre-connect connection attributes

Is it possible to set pre-connect attributes on a connection using r odbc? I want to use Active Directory access token to connect to Azure SQL Data Warehouse. Azure docs specifiy that the token needs to be given to the driver as a pre-connect attribute SQL_COPT_SS_ACCESS_TOKEN (https://docs.microsoft.c

Describe the bug
A clear and concise description of what the bug is.
如果打开不同用户的webui 在查看用户执行的sql记录时，会调到其他用户的sql记录
To Reproduce
Steps to reproduce the behavior:

1. Configurations
2. Environments
   spark2.2
3. Operations
4. See error
   

Expected behavior
A clear and

As written here, SqlDescribeCol is allowed to return 0 in the DecimalDigitsPtr parameter, but nanodbc relies on this value when formatting SQL_C_DOUBLE values to strings (in result::result_impl::get_ref_impl), leading to truncation.

https://github.com/ClickHouse/clickhouse-odbc/blob/65b059560ca18391d1725466b6e5d4a18ba088df/packaging/License.rtf

Should be updated as here:
ClickHouse/clickhouse-odbc@12e7a1b#diff-9879d6db96fd29134fc802214163b95a

Also - no way to distinguish 32 & 64 bit installations
![name_of_packages](https://user-images.githubusercontent.com/15

A useR!2017 attendee asked after the implyr talk about what Impala's limitations for using DISTINCT were. Older versions of Impala (before version 2.0) allowed only one DISTINCT clause per query. Newer versions have removed this limitation. But the current version of Impala does have the limitation that you cannot use DISTINCT in more than one aggrega

http://docs.sqlalchemy.org/en/latest/changelog/migration_12.html#support-for-sql-comments-on-table-column-includes-ddl-reflection

This should be relatively straightforward as the EXASOL dialect mirrors the ORACLE dialect. Comments on different DB objects are supported and can be set inline
CREATE TABLE foo ( ... ) COMMENT is 'a comment';
or as individual SQL
`COMMENT ON TABLE foo IS 'a ta