Thank you for the responses.
The application and stored procedures utilize a UDF.dll. Does this need
to change? Does it need to be compiled as a 64-bit .dll for the server,
but remain 32-bit on the clients?
The client application doesn't use the UDF library directly. The UDF
library must
Thank you for the responses. The application and stored procedures utilize a
UDF.dll. Does this need to change? Does it need to be compiled as a 64-bit
.dll for the server, but remain 32-bit on the clients?
Hi all,
I have volunteered to write a statistics-type program in
Lazarus/FreePascal under Linux and I need an embedded database, that
means it has to be Firebird. I've used a lot of database software
before, but never Firebird (nor Interbase, for that matter). I do NOT
want to force users to
Maybe storing it into a CHAR(22) using OCTECTS charset?
Helen's book describes octets as:
OCTETS | BINARY
Bytes which will not be interpreted as characters. Useful for storing
binary data, GUID strings, hexidecimal numbers and for correcting
string data that is causing transliteration errors.
On Mar 6, 2015, at 9:58 AM, brian br...@meadows.pair.com [firebird-support]
firebird-support@yahoogroups.com wrote:
My problem is that I must avoid duplicated records in the database,
the unique key is a complicated structure containing four 16-bit words
plus a 108-bit set of flags. The
Marco,
Maybe storing it into a CHAR(22) using OCTECTS charset?
While this will work and is the smallest storage footprint/representation.
I would recommend to sacrifice disk space and to store the key as a string
using a base 36 encoding (0-1 + A-Z) -- it makes debugging via tools much
