Am 02.05.2006 um 18:46 schrieb [EMAIL PROTECTED]:
Felix Schwarz <[EMAIL PROTECTED]> wrote:
I'm wondering whether there is a big
performance hit for a simple
SELECT binarydata FROM entries WHERE somehash = 27817298;
when I use
CREATE TABLE entries(
entry_id
If you have a wide table and want to optimize performance you would do
better to increase the page size.
JS
Jay Sprenkle wrote:
On 5/2/06, Felix Schwarz <[EMAIL PROTECTED]> wrote:
Hi,
Morning!
"Put small and frequently used columns early in the table to minimize
the need to follow the
Felix Schwarz <[EMAIL PROTECTED]> wrote:
>
> I'm wondering whether there is a big
> performance hit for a simple
>
> SELECT binarydata FROM entries WHERE somehash = 27817298;
>
> when I use
>
> CREATE TABLE entries(
> entry_id INTEGER PRIMARY KEY,
>
Felix Schwarz wrote:
Hi,
I have to decide on a table layout for storing the data of my
upcoming project.
Yesterday I have made my way through the excellent presentation at
http://www.sqlite.org/php2004/page-036.html and read the sentence
"Put small and frequently used columns early in
On 5/2/06, Felix Schwarz <[EMAIL PROTECTED]> wrote:
Hi,
Morning!
"Put small and frequently used columns early in the table to minimize
the need to follow the overflow chain."
Now, that's interesting! And I'm wondering whether there is a big
performance hit for a simple
SELECT
Hi,
I have to decide on a table layout for storing the data of my
upcoming project.
Yesterday I have made my way through the excellent presentation at
http://www.sqlite.org/php2004/page-036.html and read the sentence
"Put small and frequently used columns early in the table to minimize
6 matches
Mail list logo