Re: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-16 Thread Vitali Lovich
Sorry.. Pressed send before completing the explanation. Most of the time is spent actually just creating the db representation of the library, which is a fairly significant amount of time - it's inserting at about 3-5 mp3 files per second into the DB, but that's only a profiled release build.

Re: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-16 Thread Vitali Lovich
This actually isn't really something that really has a user interface (at least not at the moment). sourceforge.net/projects/networkmedia for the little blurb - basically I'm working on a way of synchronizing disjoint music collections - i.e. music collection on laptop, music collection on

RE: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-16 Thread Griggs, Donald
Re: "..a possible optimization I'm thinking of ..." Is it simple to place, say, 10 SQL Bind operations in series, then see if this time is even perceptible? Since this is a human interface, is it not likely that any efforts to avoid the binds will go unnoticed because the execution time is so

Re: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-16 Thread Vitali Lovich
Thanks for the helpful reply - it does seem like it'll probably be be better and easier to compile a new statement every time - a possible optimization I'm thinking of making is that I'll cache the fields selected in the previous query - that way I'll only need to recompile the query every

Re: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-16 Thread Dennis Cote
Vitali Lovich wrote: Yeah, I know I can do that, and that's my backup option. I just wasn't sure how much performance suffers in this situation because this has to keep re-compiling the SQL statements (whereas right now, all my SQL statements are only prepared once at runtime and then the

Re: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-13 Thread Vitali Lovich
Yeah, I know I can do that, and that's my backup option. I just wasn't sure how much performance suffers in this situation because this has to keep re-compiling the SQL statements (whereas right now, all my SQL statements are only prepared once at runtime and then the appropriate values are

Re: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-13 Thread Dennis Cote
Vitali Lovich wrote: Maybe there's something else I can do to get around it for my purposes. What I have for instance is a table representing ID3 tags. What I want to do is select from the table any existing tags that match a variable number of fields - for instance, I can say I want to

Re: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-13 Thread Vitali Lovich
Maybe there's something else I can do to get around it for my purposes. What I have for instance is a table representing ID3 tags. What I want to do is select from the table any existing tags that match a variable number of fields - for instance, I can say I want to match using title &

Re: [sqlite] Escaping wildcards when using LIKE & UTF-16

2006-10-13 Thread Dennis Cote
Vitali Lovich wrote: I have a statement along the lines of: "SELECT * FROM table WHERE value LIKE :abc" I want to bind a UTF-16 string to abc - however, it can potentially contain % or _ - does sqlite provide any functionality for escaping these characters (I know I have to use the escape