What is a GOTA?
Have you tried using `row.Scan()`?
Regards
On Saturday, September 9, 2017 at 12:57:14 PM UTC+5, Vikram Rawat wrote:
>
> can anybody help me out with it. I want to get this data into GOTA
> Dataframe. I just can't figure out how to get the data from SQL into GOTA
> =
could all be doing better.
>
> On Mon, Jul 31, 2017 at 8:44 PM Nigel Tao > wrote:
>
>> On Tue, Aug 1, 2017 at 6:25 AM, fazal >
>> wrote:
>> > It was one of the things I was looking forward to, but I see almost no
>> > activity there, which makes me
Thanks for the great work on exp/shiny.
Where does shiny need most attention/contributions?
I think a status report of some sort would help others pickup where it's
left off now.
On Tuesday, August 1, 2017 at 7:44:42 AM UTC+5, Nigel Tao wrote:
>
> On Tue, Aug 1, 2017 at 6:2
It was one of the things I was looking forward to, but I see almost no
activity there, which makes me sad.
Is it because it is mature enough for general use? There is a road-map for
widgets but non are complete. I really hope it is not abandoned because Go
really needs a GUI library that is id
Checkout https://github.com/ory-am/hydra for a standalone server
and https://github.com/ory-am/fosite library used in implementing the server
On Wednesday, January 11, 2017 at 12:31:11 AM UTC+5, Vasiliy Tolstov wrote:
>
> Hi! I need oauth2 server package for go. I found some of them on godoc.org
Checkout https://github.com/ory-am/hydra
On Wednesday, January 11, 2017 at 12:31:11 AM UTC+5, Vasiliy Tolstov wrote:
>
> Hi! I need oauth2 server package for go. I found some of them on godoc.org
> https://godoc.org/github.com/RangelReale/osin and
> https://godoc.org/github.com/go-oauth2/oauth2
Introducing new types just to show few details is what I'd like to avoid.
I think second approach (mine and yours) is the most flexible, idiomatic
way to go. But embedding directly has the disadvantage that all JSON fields
must be prefixed to avoid ambiguity ("org-id", "team-id").
Tagging all f
Fellow gophers,
I'm having this dilemma of whether to embed related struct, or to have an
ID field pointing to resource in the DB.
Say I have something like these types defined.
type Team struct{
ID string
Name string
}
type Organization struct {
ID string
Name string
}
Now m
Fellow gophers,
I'm having this dilemma of whether to embed related struct, or to have an
ID field pointing to resource in the DB.
Say I have something like these types defined.
type Team struct{
ID string
Name string
}
type Organization struct {
ID string
Name string
}
Now m
