| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
| |
This reverts commit bb7bddc47dd0748b45d22180d9e3c8e5209010b3
due to forward binary compatibility issues in a point release.
|
| |
|
|
| |
Reviewed-by: nrc
|
| |
|
|
| |
Best as I can determine via trial and error. It should make vc6 compile again though.
|
| |
|
|
| |
It seems that after approx version 2.7.0, microsoft changed the ODBC types of certain functions, to cater for 64bit architectures. This tries to be a little bit smarter about which types are used in which places.
|
| |
|
|
|
|
|
| |
This test has always been wrong/confusing. Fix it to work, and make sense.
Task-number: 250026
Revby: Lincoln Ramsay
|
| |
|
|
|
|
|
| |
Microsofts SQL Server odbc driver calls SET QUOTED_IDENTIFIER_ON,
but freetds doesn't, so any quoting fails. This fixes that issue.
Reviewed-by: abcd
|
| |
|
|
|
|
|
|
|
|
|
| |
If no quotes around identifiers are provided by the programmer,
identifiers are treated identically to how the underlying engine
would behave. i.e. some engines uppercase the identifiers
others lowercase them. If the programmer wants case sensitivty
and/or use whitespaces they will need to quote their identifiers.
The previous (incorrect) behaviour always quoted the identifiers.
Reviewed-by: Bill King
|
| |
|
