[sqlite] How to bind a tinyint so that actually uses 1 byte?

2008-10-24 Thread dbikash
Hi, I am using tinyint in my schema, but while doing paramterized insertion, I find that there is no specific bind API to insert a tinyint. So I used int sqlite3_bind_int() instead. However, the size of my database suggests that SQLite might actually be using 4 bytes instead of 1. Is it? How

Re: [sqlite] How to bind a tinyint so that actually uses 1 byte?

2008-10-24 Thread Cory Nelson
On Fri, Oct 24, 2008 at 2:49 AM, dbikash [EMAIL PROTECTED] wrote: Hi, I am using tinyint in my schema, but while doing paramterized insertion, I find that there is no specific bind API to insert a tinyint. So I used int sqlite3_bind_int() instead. However, the size of my database suggests

Re: [sqlite] How to bind a tinyint so that actually uses 1 byte?

2008-10-24 Thread Jay A. Kreibich
On Fri, Oct 24, 2008 at 02:49:14AM -0700, dbikash scratched on the wall: Hi, I am using tinyint in my schema, but while doing paramterized insertion, I find that there is no specific bind API to insert a tinyint. So I used int sqlite3_bind_int() instead. However, the size of my database

Re: [sqlite] How to bind a tinyint so that actually uses 1 byte?

2008-10-24 Thread [EMAIL PROTECTED]
As long as your values are within the range of -128 to +127, your integers will only take one byte of storage (plus common overhead). There's an extra byte of meta data for each column value in each row due to manifest typing, so an int will take at least 2 bytes of storage per column