Scott P. Jones

> If you really want to deal with it yourself directly I could add a "native type" which simply passes the value through to you directly. That would be great...

Actually, both memory consumption *and* performance are better, if you can use a fixed size immutable or bitstype. Julians often seem to forget the huge effect memory consumption can have...

Think of a vector of these things, the vector itself might be n * pointer size, but then you will need around 64 bytes for *each* element in the vector...

You could probably define an 8, 16, and 24 byte sizes, depending on whether the column is declared with just NUMBER (or DECIMAL), in which case it would need the...

Note: if we did want the (hardware supported on IBM platforms, nice since Julia runs on the LE Power), I could restart my attempt to get the `decimal` C library...

> So, a vector of values of type `OraNumber{x}` , for a fixed value `x` , will have memory and performance issues you're pointing out? Since there's a fixed size,...

Oh, I just thought of another thing. Maybe this numeric support should not be put into this package, but rather, a package that can be used with ODBC.jl, and another...

Ah, I see where I got confused: Oracle OLAP DML has `DECIMAL` and `SHORTDECIMAL` that match IEEE, Oracle DBMS has `DECIMAL` and `NUMBER` (which is basically the same as `NUMERIC`...

Here is a good description of the ANSI SQL numeric types: https://academy.vertabelo.com/blog/understanding-numerical-data-types-sql/ In the standard there is a small difference between `DECIMAL` and `NUMERIC`, which has to do whether the...

I'd be afraid that this would lose a requirement that the Vector be contiguous in memory (which is I believe true for the underlying SQLite C code). You might need...