Kevin Leung

Ok I figured it out: ```haxe class UserTableTools { public static function get(table:Table, id:Id) return table.where(user.id == id).first(); } ```

I think in any case it should be explicitly parsed into int (so that exceptions can be handled) before passing to tink_sql.

I wonder why though. Because even for Float there are only `Field Float` operator overloads but not `Float Field`, so I expect this will work only one way but the...

Snippet: ```haxe @:tink class Main { // uncomment either one of the following // @:forward var a:Abs; // fail // @:forward var c:Cls; // ok public static function main() {...

Any chance this will step forward a bit?

Object field name as alias is what I expected too. Welcome that. But I don't really have idea for the second one. I wonder if the upcoming (if ever) Haxe...

Seems no effect. Added a failing test btw

> Hmm, can you try putting a @:notNull on Field? Since the comparison is `false`, shouldn't it be something like `@:canBeNull` instead? Maybe we should add `table.field.isNull()` instead...

for reference: https://github.com/haxetink/tink_sql/commit/5ccc214a7859779189ec6e463577f78786709fe5 (added `isNull()`)

Pushed a bandaid fix. It sucks. But I need it quick for now. Sorry about that.