<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general">
    <title>gmane.comp.db.sqlite.general</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74489"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74488"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74487"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74486"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74485"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74484"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74483"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74482"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74481"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74480"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74479"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74478"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74477"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74476"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74475"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74474"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74473"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74472"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74471"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74470"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74489">
    <title>Re: How do you access a specific row of a resultset?</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74489</link>
    <description>&lt;pre&gt;
On 16 May 2012, at 11:14pm, Goatjugsoup &amp;lt;goatjugsoup-PkbjNfxxIARBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


SQLite is free to return rows in any order which satisfies your ORDER BY clause.  It is possible for the same SELECT statement, run twice in a row, with the same data in the table, to return its rows in a different order.  Two ways I can think of to make this happen are to create a new index, and to do an ANALYZE, but there are probably others which I haven't thought of.

If you want your rows to be returned in the same order every time, use an ORDER BY clause for your SELECT statement, and make sure the order you've asked for the rows gives every row a unique value.

Simon.
&lt;/pre&gt;</description>
    <dc:creator>Simon Slavin</dc:creator>
    <dc:date>2012-05-16T22:27:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74488">
    <title>Re: How do you access a specific row of a resultset?</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74488</link>
    <description>&lt;pre&gt;
Only if you use ORDER BY clause, and the set of columns in this clause
have unique values for each row, and all these values don't change
between query executions.


Pavel


On Wed, May 16, 2012 at 6:14 PM, Goatjugsoup &amp;lt;goatjugsoup-PkbjNfxxIARBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:
&lt;/pre&gt;</description>
    <dc:creator>Pavel Ivanov</dc:creator>
    <dc:date>2012-05-16T22:25:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74487">
    <title>Re: How do you access a specific row of a resultset?</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74487</link>
    <description>&lt;pre&gt;
Well, a new thought just came to me, if I use the same sql statement will the
resultset be in the same order each time because if that is the case I
imagine I could use a for statement and an index to move through it the way
I want to with next inside of that as many times as it takes to get to where
I need.
&lt;/pre&gt;</description>
    <dc:creator>Goatjugsoup</dc:creator>
    <dc:date>2012-05-16T22:14:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74486">
    <title>Re: Please review this email to sqlite's mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74486</link>
    <description>&lt;pre&gt;
Sorry, I misspoke here a little bit and I think it's confusing you to the 
actual problem I'm having. To clarify: After I do a commit to "otherdb" - I'm 
*still* able to atomically roll it back, simply because I keep history of its 
previous versions in the sqlite db. I have it such that if the sqlite database 
itself rolls back, then the data in otherdb automatically does as well (it 
involves lots of COW pages and such). This is a solved problem.

The real problem is that while I'm waiting for "otherdb" to synchronize, more 
data is still coming in to this entire solution. Otherdb is able to take that 
data and put it in a "future version", but sqlite can't. After otherdb 
synchronizes (i.e., with fsync), I can commit the sqlite db and even if 
otherdb has more stuff of a "future version" added to it, the sqlite database 
causes that "future data" to be safely ignored.

However, while I can safely add to otherdb's "future data", there's no place 
to add it into SQLite, as I still haven't committed sqlite'&lt;/pre&gt;</description>
    <dc:creator>Charles Samuels</dc:creator>
    <dc:date>2012-05-16T20:52:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74485">
    <title>Re: Please review this email to sqlite's mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74485</link>
    <description>&lt;pre&gt;

You will find that in almost all situations where either of them failed, whatever method you're using to protect the integrity of your data will fail too, because it will depend on the same thing.  Not only that, but that your method of assuring synchrony is likely to add lots of complication which will make the whole system fail more than a simple one-SQL-engine implementation would.  For data integrity of the type you describe, there's nothing much you can do short of using duplicate servers talking to RAIDs with redundancy.

On 16 May 2012, at 7:40pm, Charles Samuels &amp;lt;charles-zqt5JYEDRmtBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


You are inventing a versioning system for database rows.  This has been discussed a few times on this list, but never with any useful outcome in the form of code.  There's no reason it couldn't be done, but it can turn complicated fast.  Especially if you are going to deal correctly with multi-thread, multi-process or multi-user access.  Two standard approaches are savepoints and an&lt;/pre&gt;</description>
    <dc:creator>Simon Slavin</dc:creator>
    <dc:date>2012-05-16T19:20:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74484">
    <title>Re: Please review this email to sqlite's mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74484</link>
    <description>&lt;pre&gt;
Well, yes, but it already does; you can rollback a savepoint.

If I could rollback a savepoint and then unrollback it after doing an commit, 
that'd be the equivalent, if I could trick the paging module.


I'm trying that now, it involves temporary tables and views; but the 
bookkeeping for it is looking to be increasingly difficult and it is also going 
to make my own code unmaintainable.

I'm willing to pay the sqlite team to add this feature to a future of sqlite.

Charles

p.s. please excuse my Subject line.
&lt;/pre&gt;</description>
    <dc:creator>Charles Samuels</dc:creator>
    <dc:date>2012-05-16T18:40:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74483">
    <title>Re: Please review this email to sqlite's mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74483</link>
    <description>&lt;pre&gt;
Well, SQLite doesn't. Basically, you want SQLite to maintain multiple 
not-yet-committed versions of the same record. I don't believe there's 
any way to get it to do that automatically - you'll have to come up with 
an explicit versioning scheme (like your idea of creating a temporary 
shadow database).


"Oh yes, I thought of something... but unfortunately, it rather involved 
being on the other side of this airtight hatchway." -- The Hitchhiker's 
Guide to the Galaxy.
&lt;/pre&gt;</description>
    <dc:creator>Igor Tandetnik</dc:creator>
    <dc:date>2012-05-16T17:37:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74482">
    <title>Re: Query by License -Consulta por Licencia</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74482</link>
    <description>&lt;pre&gt;Guillermo:

Due to generous copyright conditions of its author DRH, you can use SQLite in any application you want and for any purpose.

HTH

&lt;/pre&gt;</description>
    <dc:creator>ajm-CVOehM+pzcwAvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-05-16T17:14:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74481">
    <title>Re: Please review this email to sqlite's mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74481</link>
    <description>&lt;pre&gt;
Yes, but this is incredibly hard: I have to maintain the schema twice, I can't 
allow the user to enter their own SQL statements, I still have to copy all the 
accumulated stuff over, and schema changes would be very difficult to handle.

Charles
&lt;/pre&gt;</description>
    <dc:creator>Charles Samuels</dc:creator>
    <dc:date>2012-05-16T17:03:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74480">
    <title>Re: How do you access a specific row of a resultset?</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74480</link>
    <description>&lt;pre&gt;The other thing you are not thinking about is that you never know the order of data in a set.  You may think that you want the 5th record that was ever inserted into the table, but you have no guarantee that a select statement will return records in the order in which they were inserted.  The 5th oldest record could come up first in the result set, or last, or anywhere else.

So, you either have to walk through the set from the beginning, checking every record to see if it's the one you want, or you're going to have to build a more precise select statement.

RobR
&lt;/pre&gt;</description>
    <dc:creator>Rob Richardson</dc:creator>
    <dc:date>2012-05-16T15:24:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74479">
    <title>Re: Please review this email to sqlite's mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74479</link>
    <description>&lt;pre&gt;Did you check out
http://www.sqlite.org/inmemorydb.html

Could you use an in-memory db to act as a db for a save point?

When you are ready to commit, do so from 1 in memory db, while accumulating
into another in preparation for that save point.

Adam

On Tue, May 15, 2012 at 1:55 PM, Charles Samuels &amp;lt;charles-zqt5JYEDRmtBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:




&lt;/pre&gt;</description>
    <dc:creator>Adam DeVita</dc:creator>
    <dc:date>2012-05-16T14:10:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74478">
    <title>Re: How do you access a specific row of a resultset?</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74478</link>
    <description>&lt;pre&gt;
That rather depends on what "it" is. What's the point of the exercise? Are you looking to implement something like this, by any chance:

http://www.sqlite.org/cvstrac/wiki?p=ScrollingCursor

&lt;/pre&gt;</description>
    <dc:creator>Igor Tandetnik</dc:creator>
    <dc:date>2012-05-16T13:51:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74477">
    <title>Re: import problem</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74477</link>
    <description>&lt;pre&gt;

Donald Griggs ha scritto quanto segue il 16/05/2012 13.24&amp;gt;

1744:
i have the last line as the previous.
I tryed with and without the carriage return but i have this error.

82886:
i have many " unclosed.
do it is possible to bypass the congruity check and import as in 
previous version in special cases?


 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Speciale ponte del 2 Giugno a Cesenatico all'Hotel Gallia: Pacchetto 2 giorni: Euro 154; Pacchetto 3 giorni: Euro 231. Pensione completa, servizio spiaggia, bevande ai pasti
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=12343&amp;amp;d=16-5
&lt;/pre&gt;</description>
    <dc:creator>Spora</dc:creator>
    <dc:date>2012-05-16T13:14:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74476">
    <title>Re: NULL sqlite3_stmt in function calls</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74476</link>
    <description>&lt;pre&gt;

No.  sqlite3_finalize() is, but most others are not.





&lt;/pre&gt;</description>
    <dc:creator>Richard Hipp</dc:creator>
    <dc:date>2012-05-16T12:48:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74475">
    <title>Re: Query by License -Consulta por Licencia</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74475</link>
    <description>&lt;pre&gt;2012/5/16 Guillermo Soland &amp;lt;ggsoland-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;:

http://www.sqlite.org/copyright.html


Regards,
Simon
&lt;/pre&gt;</description>
    <dc:creator>Simon Davies</dc:creator>
    <dc:date>2012-05-16T12:46:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74474">
    <title>Re: Escape table and column names</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74474</link>
    <description>&lt;pre&gt;
At 13:55 16/05/2012, you wrote:
´¯¯¯
`---

Oops, that's what happens when you try doing too many things at the 
same time.

Nonetheless,

SQLite version 3.7.11 2012-03-20 11:35:50
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite&amp;gt; create table [foo [[bar]] ?] (a);
Error: unrecognized token: "]"

It would be logical to have ]] represent a single ] (standard escape by 
doubling), while [[ would be left as [[ since there's ne need to escape 
the opening bracket [.

But yes, this one works:

sqlite&amp;gt; create table `foo ``bar`` ?` (a);
sqlite&amp;gt; &lt;/pre&gt;</description>
    <dc:creator>Jean-Christophe Deschamps</dc:creator>
    <dc:date>2012-05-16T12:38:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74473">
    <title>Re: Accented chars in Android embeded Sqlite.</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74473</link>
    <description>&lt;pre&gt;

There is a file in the latest source tree named "test_spellfix1.c" which
includes an application-defined SQL function named
"spellfix1_translit(X)".  See
http://www.sqlite.org/src/artifact/495535f3eb57a?ln=1152-1171 for the
implementation.  The spellfix1_translit(X) function attempts to convert its
input string X into a pure ASCII transliteration.  In other words, it
removes the accented characters, replacing them with ASCII equivalents.
Example:

      SELECT spellfix1_translit('água');     -- returns agua

You could, perhaps, add such a function to your application, then use it to
accomplish what you describe above:

      SELECT * FROM table WHERE spellfix1_tanslit(column) LIKE 'a%';

Note that spellfix1 is not currently a part of any build and is
unsupported.  But you can use it as a guide to your own implementation.





&lt;/pre&gt;</description>
    <dc:creator>Richard Hipp</dc:creator>
    <dc:date>2012-05-16T12:27:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74472">
    <title>Re: sqlite max query parameters differs on Snow Leopard?</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74472</link>
    <description>&lt;pre&gt;

The upper limit on the maximum number of query parameters is a compile-time
parameter that defaults to 999.  Apple raises the limit to 500,000 in their
builds of SQLite.

SQLite allocates an array to hold query parameters.  The size of the array
is the size of the largest parameter.  So you really don't want to be using
?500000 as that requires a large allocation, even if it is the only query
parameter used. The engineers at Apple are aware of this issue but still
choose to increase the limit to 500000 since apparently there exist legacy
applications on their platform that require this large limit.




To find the upper bound use:

    sqlite3_limit(db, SQLITE_LIMIT_VARIABLE_NUMBER, 0x7fffffff);
    int upperBound = sqlite3_limit(db, SQLITE_LIMIT_VARIABLE_NUMBER, -1);





&lt;/pre&gt;</description>
    <dc:creator>Richard Hipp</dc:creator>
    <dc:date>2012-05-16T12:19:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74471">
    <title>import problem</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74471</link>
    <description>&lt;pre&gt;I have problem when import with versione superior to 3071000.
No problem with 3071000.

..\sqlite3 -echo aa_VUOTO.db   0&amp;lt;aa.script
.separator "\t"
.import aa.txt aa
Error: aa line 1744: expected 5 columns of data but found 2
.import aa aa
Error: aa.txt line 82886: expected 9 columns of data but found 5
.exit
 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Fino al 2 Giugno una settimana Euro 310 nel Family Hotel King di Milano Marittima. Speciale settimana corta con arrivo la domenica e partenza al sabato Euro 270. Pensione completa, bevande ai pasti, terzo letto gratis, quarto scontato 50%, servizio spiaggia
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=12340&amp;amp;d=16-5
&lt;/pre&gt;</description>
    <dc:creator>Spora</dc:creator>
    <dc:date>2012-05-16T10:19:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74470">
    <title>Accented chars in Android embeded Sqlite.</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74470</link>
    <description>&lt;pre&gt;Hi everyone!

Im Brazilian, also, Android Dev.

Im in a struggle with Sqlite and accented chars such as á or é.

What Im trying to do is a select with where accent insensitive.

For months I have having research over and over the internet to accomplish
that, but, unfortunately unsuccessful.

 

What I need is something like this:

select * from table where column like a%

and result be:

agora

água

através

and so on

 

Its possible? Or better to commit suicide ;-)

Thanks in advance

Youre all aces in my book.

 &lt;/pre&gt;</description>
    <dc:creator>Yahoo</dc:creator>
    <dc:date>2012-05-16T01:23:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.sqlite.general/74469">
    <title>Query by License -Consulta por Licencia</title>
    <link>http://permalink.gmane.org/gmane.comp.db.sqlite.general/74469</link>
    <description>&lt;pre&gt;Mr. Representative of SQLite:


Hello, my name is Guillermo G. Soland, I live in the city of Villa
Constitución, Santa Fe, Argentina, I graduated as a Computer Systems Analyst,
but now I do not practice my profession for profit because my job is totally
alien to what I studied , he wanted to see if I am allowed to include a file
SQLite database in an application that I developed, and if so if I'm allowed
to include with the application to apply for registration under any license,
either GPL or Copyright (preferably the latter).
Motivates this reason that I like to develop applications (as amateur) to
users or public organizations, usually non profit with the sale of software
(do not sell, are free), but I would ever write a history that I have I
performed.
From already thank you very much.



Signed:  Guillermo G. Soland







(Texto Original en Español)


Sr. Representante de SQLite:


Hola, me llamo Guillermo G. Soland,  vivo en la ciudad de Villa
Constitución, provincia de Santa Fe, Argentina, soy gra&lt;/pre&gt;</description>
    <dc:creator>Guillermo Soland</dc:creator>
    <dc:date>2012-05-16T00:35:49</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.db.sqlite.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.db.sqlite.general</link>
  </textinput>
</rdf:RDF>

