Re: [sqlite] Reducing size

2012-09-13 Thread Dmitry Baryshev
2012/9/12 Simon Slavin > > On 12 Sep 2012, at 8:00pm, Dmitry Baryshev wrote: > > > Actually this is a dynamically loaded plugin, so compiler won't strip > > unused functions. I cannot change this behaviour. That's why I'm asking > > about SQLITE_* directives. > > Ah. In that case you want secti

Re: [sqlite] Reducing size

2012-09-12 Thread Simon Slavin
On 12 Sep 2012, at 8:00pm, Dmitry Baryshev wrote: > Actually this is a dynamically loaded plugin, so compiler won't strip > unused functions. I cannot change this behaviour. That's why I'm asking > about SQLITE_* directives. Ah. In that case you want section 1.6 of

Re: [sqlite] Reducing size

2012-09-12 Thread Dmitry Baryshev
2012/9/12 Simon Slavin > > On 12 Sep 2012, at 7:05pm, Rob Richardson > wrote: > > > Why are you concerned about the size of sqlite3.o? > > Or, to clarify Rob's question, modern compiler chains include only code > for routines which are referred to from main() on down. If no part of your > code

Re: [sqlite] Reducing size

2012-09-12 Thread Simon Slavin
On 12 Sep 2012, at 7:05pm, Rob Richardson wrote: > Why are you concerned about the size of sqlite3.o? Or, to clarify Rob's question, modern compiler chains include only code for routines which are referred to from main() on down. If no part of your code refers to sqlite3_status() then it ne

Re: [sqlite] Reducing size

2012-09-12 Thread Rob Richardson
Why are you concerned about the size of sqlite3.o? RobR ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Reducing size

2012-09-12 Thread Dmitry Baryshev
Hi. I use a sqlite database in read-only mode. The database itself contains just one table with an unique key, several strings and a double number per row: 0 'book1' 'author1' 10.00 1 'book2' 'author2' 12.05 2 'book3' 'author3' 9.35 ... I use just the following SQL commands in my application to

Re: [sqlite] Reducing size of timestamps

2008-02-22 Thread John Stanton
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

Re: [sqlite] Reducing size of timestamps

2008-02-22 Thread Dennis Cote
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

Re: [sqlite] Reducing size of timestamps

2008-02-22 Thread John Elrick
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

[sqlite] Reducing size of timestamps

2008-02-22 Thread Rich Rattanni
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,