Re: [sqlite] Maximum length of the field name

Hi, AFAIK, there is no limit. At least, browsing http://www.sqlite.org/limits.html, I found none. The maximum length of an SQL statement, 100 by default, limits the column names you can use, because you have to issue a "create table" - statement. Martin Ev wrote: > What's the maximum

[sqlite] Maximum length of the field name

What's the maximum length of the field name for sqlite? Thank you. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] sqlite-users Digest, Vol 23, Issue 15

Peter Haworth wrote: > Interesting you should classify my data need as a waste without > knowing anything about my application. What if I want to calculate a > percentage that the first column is of the total - would it still be a > waste to calculate the total? Yes, it would be a waste to

Re: [sqlite] Why does LIKE operator affect order of query plan?

On Sun, Nov 15, 2009 at 11:41 AM, P Kishor wrote: > On Sun, Nov 15, 2009 at 10:39 AM, Tim Romano wrote: >> I have a query with joined inline views that runs in about 100ms against >> a 4 million row table joined to a 275,000 row table.  Not bad, SQLite

Re: [sqlite] sqlite-users Digest, Vol 23, Issue 15

Thank you Kees. While not achieving exactly what I was thinking of (the total is in an extra row at the end of the selected rows rather than a column in each row), this will work for me. Pete Haworth http://www.mollysrevenge.com http://www.sonicbids.com/MollysRevenge

Re: [sqlite] Why does LIKE operator affect order of query plan?

On Sun, Nov 15, 2009 at 1:19 PM, Tim Romano wrote: > Thanks for the reply. > > A follow question:   I can understand why ... myColumn LIKE "%foo%" > ...   would have to do a full scan but shouldn't  ...myColumn LIKE > "foo%" ...  be able to use an index? > > see Section 4

Re: [sqlite] Why does LIKE operator affect order of query plan?

Thanks for the reply. A follow question: I can understand why ... myColumn LIKE "%foo%" ... would have to do a full scan but shouldn't ...myColumn LIKE "foo%" ... be able to use an index? P Kishor wrote: > On Sun, Nov 15, 2009 at 10:39 AM, Tim Romano wrote: >

Re: [sqlite] sqlite-users Digest, Vol 23, Issue 15

On Sun, Nov 15, 2009 at 12:34 PM, Peter Haworth wrote: > Interesting you should classify my data need as a waste without > knowing anything about my application.  What if I want to calculate a > percentage that the first column is of the total - would it still be a > waste

Re: [sqlite] sqlite-users Digest, Vol 23, Issue 15

On Sun, Nov 15, 2009 at 12:25 PM, Peter Haworth wrote: > Thanks for the suggestion.  Unfortunately, unless I'm doing something > wrong, this seems to result in just one row being returned showing the > sum amount. > That is what its supposed to do... a few suggestions --

Re: [sqlite] sqlite-users Digest, Vol 23, Issue 15

Interesting you should classify my data need as a waste without knowing anything about my application. What if I want to calculate a percentage that the first column is of the total - would it still be a waste to calculate the total? As far as I'm concerned , the more data manipulation

Re: [sqlite] sqlite-users Digest, Vol 23, Issue 15

Thanks for the suggestion. Unfortunately, unless I'm doing something wrong, this seems to result in just one row being returned showing the sum amount. Pete Haworth On Nov 15, 2009, at 4:00 AM, sqlite-users-requ...@sqlite.org wrote: > Date: Sat, 14 Nov 2009 14:17:18 -0600 > From: P Kishor

Re: [sqlite] Why does LIKE operator affect order of query plan?

On Sun, Nov 15, 2009 at 10:39 AM, Tim Romano wrote: > I have a query with joined inline views that runs in about 100ms against > a 4 million row table joined to a 275,000 row table.  Not bad, SQLite :-) > > But when I use the LIKE operator instead of the = operator, the

[sqlite] Why does LIKE operator affect order of query plan?

I have a query with joined inline views that runs in about 100ms against a 4 million row table joined to a 275,000 row table. Not bad, SQLite :-) But when I use the LIKE operator instead of the = operator, the order of the query plan changes, though the same indexes are involved, and the

Re: [sqlite] Help me please to optimize sql query

Thank you, Simon! Could you please say me what indexes will be correct? I'm trying CREATE INDEX mgwrInd1 ON mgWordsRelations (id_norm) CREATE INDEX mgwrInd2 ON mgWordsRelations (id_norminrel) CREATE INDEX wfInd1 ON wform (wordForm) CREATE INDEX wfInd2 ON wform (wordNorm) CREATE INDEX wfInd3 ON

Re: [sqlite] Help me please to optimize sql query

Thank you very much! It works well! Igor Tandetnik wrote: > > Try this: > > select wf1.wordForm > from wform wf1 join mgWordsRelations rel on (wf1.wordNorm = > rel.id_norminrel) > join wform wf2 on (rel.id_norm = wf2.wordNorm) > where wf1.ancode = 'someAncode' and wf2.wordForm =

Re: [sqlite] german documentation

That's one point. I also prefer the german version instead of an english one. It's almost better to understand if there are many technic related words and topics in it. I searched for an community or something like that, but i didn't found one, so i started a new project for what. I know, i have

Re: [sqlite] german documentation

Marcus Grimm schrieb: > this will be a lot of work and I'm wondering why > you do this ? > Despite beeing a german with a rather poor english knowledge, > I guess a programmer should still be able to understand > the english sqlite documentation, right ? :-) > There are still lots of