Add capability to check if numbers are unsigned when using CodeGen #1769
Comments
Asamsig
pushed a commit
to Asamsig/slick
that referenced
this issue
Sep 2, 2017
Added unsigned integer mapping to Long, following the MySQL connector reference. Added code for unsigned bigint aswell, but scala.math.BigInt isn't support as a default datatype, I left these parts in for completeness, but commented out. Updated the tests for the MySQLProfile to cover the new conversion. Additionally fixed two typos, I spotted randomly.
trevorsibanda
added a commit
that referenced
this issue
Sep 2, 2017
issue #1769 Add support in the MySQLProfile for UNSIGNED INT
|
After investigating it doesn't seem like any of the other database than MySQL actually uses the UNSIGNED notation, so I guess this issue can be closed. Anybody who can confirm my findings? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when using CodeGen, with for example MySQL, if you have a table like:
CREATE TABLE my_table ( id UNSIGNED INT NOT NULL AUTO_INCREMENT PRIMARY KEY, something VARCHAR(100) )It will generate a case class with
idas a Scala Int, instead CodeGen should be able to read that it is anUNSIGNED INTand cast it to a Long instead, same goes for anUNSIGNED BIGINTwhich should be cast to a BigInteger and so on.For a full list of what
SIGNED/UNSIGNEDnumbers should be cast to see here.The text was updated successfully, but these errors were encountered: