tink_sql icon indicating copy to clipboard operation
tink_sql copied to clipboard

Specifying length for integer is basically useless

Open kevinresol opened this issue 7 years ago • 3 comments

I just realized it: https://stackoverflow.com/questions/5634104/what-is-the-size-of-column-of-int11-in-mysql-in-bytes/27519793#27519793

Maybe we should consider removing the type parameter, and use Haxe's Int type instead. (But could add TinyInt, etc)

kevinresol avatar May 11 '18 14:05 kevinresol

In fact, I think we should support all basic Haxe data types and map them to the most sensible db type. But still allow using the specialized types in Types. Any comments @benmerckx @jasononeil @back2dos ?

kevinresol avatar May 11 '18 14:05 kevinresol

I had no idea. Good to know ^^

In fact, I think we should support all basic Haxe data types and map them to the most sensible db type.

Definitely. If we could have typedef BigInt = haxe.Int64 that'd be pretty cool, but I suppose that depends on the drivers.

back2dos avatar May 11 '18 18:05 back2dos

In fact, I think we should support all basic Haxe data types and map them to the most sensible db type.

That'd be nice, because the structures are often used elsewhere (clientside) too.

benmerckx avatar May 12 '18 10:05 benmerckx