Use the Sqlite method, a floating point number. Inbuilt functions
support that technique.
Rich Rattanni wrote:
> All:
>
> I was wondering if there was any way to reduce the 'cost' of storing a
> timestamp on entries in a SQLite database. I performed a hexdump of
> the file and it showed me the
Rich Rattanni wrote:
>
> I was wondering if there was any way to reduce the 'cost' of storing a
> timestamp on entries in a SQLite database. I performed a hexdump of
> the file and it showed me the timestamp is stored as a 19-byte ASCII
> string. One quick thing I thought of was to store the uni
Rich Rattanni wrote:
> All:
>
> I was wondering if there was any way to reduce the 'cost' of storing a
> timestamp on entries in a SQLite database. I performed a hexdump of
> the file and it showed me the timestamp is stored as a 19-byte ASCII
> string. One quick thing I thought of was to store t
All:
I was wondering if there was any way to reduce the 'cost' of storing a
timestamp on entries in a SQLite database. I performed a hexdump of
the file and it showed me the timestamp is stored as a 19-byte ASCII
string. One quick thing I thought of was to store the unix timestamp
in each field,
4 matches
Mail list logo
