Matt Hicks
Matt Hicks
That's a good idea. Would you be willing to submit a PR to add that functionality?
@mkotsbak, the only problem I have with using `DATETIME` is that it requires 8 bytes instead of 4 bytes, but that's hardly a big deal and given the confusion dealing...
This is a worthwhile read comparing the distinctions: http://infopotato.com/blog/index/datetime_vs_timestamp
That's possible now.
``` scala createColumn("MY_TABLE", "STAGE", Default("0")) ```
That's only available in the 1.2 snapshot though I believe.
Agreed we need `alterColumn` support.
The biggest hurdle is going to be keeping the `Session` alive across multiple asynchronously running database requests.
I agree.
The problem with a two-step process is that the queries can't then be pre-defined to return a specific mapping whether that be a `Tuple` or a specific case class.