Simply said: So Sqlite doesn't support real BCD values.
Yes, SQLite does not support them native
So we can't support it either for Sqlite.
It was my question. We can (if we want) partialy add work-arounds:
DECIMAL(x,y)
if y=0 then map to ftLargeInt (64bit integer)
elseif y=4 then map to
Joost van der Sluis schrieb:
That's why I mentioned or any other structured format.
It's not a bad idea to see if we can make a structured (and readable)
format to create our fpmake.pp files.
I was also thinking about letting fpmake detect from the compiler-output
if a dependency is missing,
Marco van de Voort schrieb:
In a new approach I'd provide the interpretation of existing MakeFiles,
and extend it to the specific needs and capabilities of the FPC/Lazarus
project (package...) model.
Personally I don't think the core makefile principles are worth preserving
at all:
ACK. A
On Fri, 2011-04-01 at 11:13 +0200, LacaK wrote:
Simply said: So Sqlite doesn't support real BCD values.
Yes, SQLite does not support them native
Then it's up to the 'user' (in our case the user is a programmer) to
implement workarounds. If we add some work-around, nobody will know that
that
No, map to ftfmtbcd, as it should. That will work fine as long as the
values are within the sqlite-range.
ok. in reading phase no problem
(ATM we read using sqlite3_column_text (so SQLite converts all storage
classes (integer,real, blob) to string) and then converting to TBCD ... ok
Let me please once more explain what I meant (I am not sure id I explained it enought)1.) When we decalre column like DECIMAL or NUMERIC then this columns will have numeric affinity2.) Columns with numeric affinity can hold only INTEGER, REAL or BLOB data (in theory they can hold also TEXT data,
Hi all,
I've just committed a change in the Makefiles for the fcl-web package.
The Makefile now calls fpmake to build and install the package.
It's a first test, so please try and report any problems you have when
building the fcl-web package. (Or all packages, or just a complete
fpc-checkout)
LacaK schrieb:
So as long as users
can't make tables with numeric fields that support more then 15 numbers,
we don't have to support bcd-fields. So map decimal to BCD (not float,
it will be invalid for values within the supported precision range). If
users want to store numbers with an higher
