Peter Magnusson
Peter Magnusson
Hi @dsniper, what kind of tests are you missing. Preferably there should be some tests for mssql but that is not one of the database engines in the default test...
I have been dabbling with adding mssql into sqlx_test.go but I keep having issues with general database syntax differences like. 1. mssql uses `SELECT TOP(1)...` instead of ending with `......
As for me this PR is ready to be merged. I'll gladly write some more tests later when and if the testing framework support mssql.
To write proper tests one would need to know how these devices supporting the methods are supposed to work or at least be configured. So, anybody who knows how to...
I like promises alot.... using https://github.com/kriskowal/q for example. But perhaps later and definitely not replacing normal callbacks. I would be happy if we could get those sorted out first. Promises...
I would possibly move this to a later milestone and get node style callbacks stabilized first.
It's no question about doing it or not, if you ask me. It's a matter of time :)
Exactly as @luchaninov describes. To be able to extend and include without absolute paths is a minimum. Some kind of "by convention" or configurable search paths would be nice.
It's noted in sqlite/sqlite.go that ``` // +build !darwin // This package depends on go-sqlite3 which wraps the C library which I can't // get to build for mac so...
My guess from debugging is that the data type is `[decimal](9,3)`. It seems to be a column of that type that fails.