Re: TinyTDS Adapter default configuration: Consider using `SET ANSI DEFAULTS` ?

2017-03-10 Thread Jeremy Evans
On Friday, March 10, 2017 at 10:04:02 AM UTC-8, Tim Tilberg wrote: > > In the short term, do you think it would be helpful to add some of this > information into the docs somewhere? (Here? > ) > > I was

Re: TinyTDS Adapter default configuration: Consider using `SET ANSI DEFAULTS` ?

2017-03-10 Thread Tim Tilberg
Sorry, I must have edited this little bit out: SSMS is the primary interface most people interact with SQL Server from -- so to me it would make sense to have behavior similar to what you'd find when running queries in SSMS. On Friday, March 10, 2017 at 12:04:02 PM UTC-6, Tim Tilberg wrote: >

Re: TinyTDS Adapter default configuration: Consider using `SET ANSI DEFAULTS` ?

2017-03-10 Thread Tim Tilberg
In the short term, do you think it would be helpful to add some of this information into the docs somewhere? (Here? ) I was surprised and frustrated when I couldn't figure out what was going on, since it was

Re: TinyTDS Adapter default configuration: Consider using `SET ANSI DEFAULTS` ?

2017-03-03 Thread Jeremy Evans
On Friday, March 3, 2017 at 10:18:30 AM UTC-8, Tim Tilberg wrote: > > Yesterday I was using Sequel to export some data from MS SQL Server using > a bunch of sprocs. Within these sprocs were statements that create temp > tables and I kept coming across: > > column does not allow nulls. INSERT

TinyTDS Adapter default configuration: Consider using `SET ANSI DEFAULTS` ?

2017-03-03 Thread Tim Tilberg
Yesterday I was using Sequel to export some data from MS SQL Server using a bunch of sprocs. Within these sprocs were statements that create temp tables and I kept coming across: column does not allow nulls. INSERT fails.