Re: [sqlite] Question about speed of CASE WHEN

2007-03-20 Thread bartsmissaert
> Or is it just a case of needing to view > the final data in a user friendly environment? That is it. They can format, sort, print etc. in Excel. They won't even have to know about SQLite. The SQLite database file can safely be deleted and it will still work the same. RBS > Hi RBS, > >> I use

Re: [sqlite] Question about speed of CASE WHEN

2007-03-19 Thread T
Hi RBS, I use SQLite as a data manipulator, not as a database. I get data from a server database, dump to SQLite, manipulate the data and finally dump to Excel. As this is reporting software speed is important, so I will go with the fastest method. OK, I have to ask. What do you then do

RE: [sqlite] Question about speed of CASE WHEN

2007-03-18 Thread RB Smissaert
[mailto:[EMAIL PROTECTED] Sent: 18 March 2007 23:46 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Question about speed of CASE WHEN RB Smissaert wrote: > Ok, now done some better testing and the method with CASE WHEN is indeed, as > expected a bit faster To me the lookup table method

Re: [sqlite] Question about speed of CASE WHEN

2007-03-18 Thread Gerry Snyder
RB Smissaert wrote: Ok, now done some better testing and the method with CASE WHEN is indeed, as expected a bit faster To me the lookup table method seems like exactly what a relational database is used for. The CASE WHEN would have to be dramatically faster, and in an area where

RE: [sqlite] Question about speed of CASE WHEN

2007-03-18 Thread RB Smissaert
Message- From: RB Smissaert [mailto:[EMAIL PROTECTED] Sent: 18 March 2007 17:17 To: sqlite-users@sqlite.org Subject: RE: [sqlite] Question about speed of CASE WHEN Done some testing now and surprisingly, it seems the lookup method with a join to a lookup table is very slightly faster than the CASE

RE: [sqlite] Question about speed of CASE WHEN

2007-03-18 Thread RB Smissaert
'Issue > when 2 then 'Note' Etc But didn't get that to work as it always produced the first WHEN option. RBS -Original Message- From: Christian Smith [mailto:[EMAIL PROTECTED] Sent: 18 March 2007 15:29 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Question about speed of CASE

RE: [sqlite] Question about speed of CASE WHEN

2007-03-18 Thread RB Smissaert
Sorry, had to rush off and missed your alternative. Will do some testing now. RBS -Original Message- From: T [mailto:[EMAIL PROTECTED] Sent: 18 March 2007 14:55 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Question about speed of CASE WHEN Hi RBS, >> Perhaps the alternativ

Re: [sqlite] Question about speed of CASE WHEN

2007-03-18 Thread Christian Smith
RB Smissaert uttered: Looking at the fastest way to convert a field in a table and wonder if in general an update with a CASE WHEN construction or an update with a join to a lookup table is faster. My guess is that the CASE WHEN form will be faster for small number of possibilities. It

Re: [sqlite] Question about speed of CASE WHEN

2007-03-18 Thread T
Hi RBS, Perhaps the alternative form of the CASE statement would be faster What form is that? The form that I showed in my previous email. That is, using: case ENTRY_TYPE when 9 then 'Issue when 2 then 'Note' etc instead of: case when ENTRY_TYPE = 9 then

Re: [sqlite] Question about speed of CASE WHEN

2007-03-18 Thread T
Hi RBS, Looking at the fastest way to convert a field in a table and wonder if in general an update with a CASE WHEN construction or an update with a join to a lookup table is faster. Perhaps the alternative form of the CASE statement would be faster, but I don't know: case ENTRY_TYPE