Color is a 32-bit
Int, so just save it as such in your SQL table.
Conceptually, behind the scenes, those 32 bits are partitioned into four individual 8-bit numbers (ie bytes), which each has a range of 0..255 (decimal) = 00..FF (hex) = 00000000..11111111 (binary). Three of these numbers are the red, green and blue intensity levels (where 0 = off ie black, 255 = full intensity, 128 = half-intensity), and the fourth number is often the alpha value (where 0 = transparent, 255 = opaque/solid, 128 = 50% translucent).
These numbers are often DISPLAYED in hexadecimal rather than decimal, eg as FF7FFFD4 rather than 4286578644, because that makes it easier to see the 8-bit numbers within, eg, I can see that the alpha value is FF (hex) = solid/non-transparent.
The "0x" at the front is the C/Java way of saying: this is a hexadecimal number. Most BASICs use "&H" to indicate hexadecimal numbers, but because B4A/J has both Java and BASIC heritage, and presumably because it was easier to transliterate, B4A/J uses the "0x" way. Personally, I would have preferred that compatibility decisions defaulted to minimizing the differences for people migrating from VB etc, but on the bright side, look upon it as broadening your linguistic arena ;-)
I have somebody in the background going on about latest Brexit yo-ha, so I've had some trouble concentrating on writing clearly here. In summary: "As Int"