Re: [go-nuts] Re: State of the database drivers in go

2017-01-13 Thread Daniel Theophanes
If you are using database/sql in a fresh project, I highly recommend starting on go1.8 (the first release candidate is out now). Also, if you encounter fundamental blocking issues with the database/sql package, please send a message to: https://groups.google.com/forum/#!forum/golang-sql Thanks,

Re: [go-nuts] Re: State of the database drivers in go

2017-01-13 Thread Henrik Johansson
Honestly I have had some less than pleasant incidents with Mongodb as well but the fault was due to simply overusing it for stuff it's not meant for. On Fri, Jan 13, 2017, 14:36 Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Fri, 13 Jan 2017 13:20:28 + > Henrik Johansson

Re: [go-nuts] Re: State of the database drivers in go

2017-01-13 Thread Konstantin Khomoutov
On Fri, 13 Jan 2017 13:20:28 + Henrik Johansson wrote: > > > I have read good reviews for mgo but i have not used it personally > > > > Okay, there's a negavite one to balance your fascination ;-) > > > > http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-never-ever-ever-use-mongodb/ >

Re: [go-nuts] Re: State of the database drivers in go

2017-01-13 Thread snmed
Hi Konstantin I'm absolutely aware of the impact of a NoSql database and how a datastructure has to be design for an effectiv use of MongoDb, but thank you anyway for your contribution. Cheers Am Freitag, 13. Januar 2017 14:08:39 UTC+1 schrieb Konstantin Khomoutov: > > On Thu, 12 Jan 2017 18:4

Re: [go-nuts] Re: State of the database drivers in go

2017-01-13 Thread Henrik Johansson
That's Mongodb itself, not the Go driver. On Fri, Jan 13, 2017, 14:08 Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Thu, 12 Jan 2017 18:42:38 +0300 > Josh Kamau wrote: > > [...] > > I have read good reviews for mgo but i have not used it personally > > Okay, there's a negavi

Re: [go-nuts] Re: State of the database drivers in go

2017-01-13 Thread Konstantin Khomoutov
On Thu, 12 Jan 2017 18:42:38 +0300 Josh Kamau wrote: [...] > I have read good reviews for mgo but i have not used it personally Okay, there's a negavite one to balance your fascination ;-) http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-never-ever-ever-use-mongodb/ [...] -- You rece

Re: [go-nuts] Re: State of the database drivers in go

2017-01-13 Thread snmed
Thats great to hear, i will start a prototype of the project with postgres and mongodb. Then i will see if our needs are satisfied and if we stay with go. :-) I really hope it is working out for us, i would prefer to use go now and in the future:-D Cheers Am Donnerstag, 12. Januar 2017 16:42:52

Re: [go-nuts] Re: State of the database drivers in go

2017-01-12 Thread Josh Kamau
I have an app in production using Postgres. The library has never been a problem. I have read good reviews for mgo but i have not used it personally Josh On Thu, Jan 12, 2017 at 6:39 PM, Henrik Johansson wrote: > Mgo https://labix.org/mgo seems to be very well maintained. > > tors 12 jan. 20

Re: [go-nuts] Re: State of the database drivers in go

2017-01-12 Thread Henrik Johansson
Mgo https://labix.org/mgo seems to be very well maintained. tors 12 jan. 2017 kl 16:26 skrev snmed : > Thank you for your answer, so far i think at least for the rdbms there are > maintained drivers. So i need just a reliable NoSql Driver for a > Document-Based Storage. > Go is awesome i hope the

[go-nuts] Re: State of the database drivers in go

2017-01-12 Thread snmed
Thank you for your answer, so far i think at least for the rdbms there are maintained drivers. So i need just a reliable NoSql Driver for a Document-Based Storage. Go is awesome i hope the eco system will grow in the future and the language can stand against rust and the omni present of c/c++.