, but as is I'm sure it will be fine with just the runtime checks.
Thanks!
- Deon
-Original Message-
From: sqlite-users On Behalf Of
David Raymond
Sent: Thursday, September 20, 2018 9:07 AM
To: SQLite mailing list
Subject: Re: [sqlite] Another Partial Index optimization opportunity (INSERT
e-users-boun...@mailinglists.sqlite.org] On
Behalf Of Deon Brewis
Sent: Thursday, September 20, 2018 11:30 AM
To: SQLite mailing list
Subject: [sqlite] Another Partial Index optimization opportunity (INSERT)
Hi, I previously reported that an UPDATE of a table containing an Expression
and/or Partial Index will unneces
Hi, I previously reported that an UPDATE of a table containing an Expression
and/or Partial Index will unnecessarily touch the expression and/or partial
index. I see both are now fixed in the 3.26.0 2018-09-19 codebase. Thank you so
much - it works great!
However, while testing it, I also
Should be fixed on trunk.
On 4/7/17, Simon Slavin wrote:
>
>> On 8 Apr 2017, at 12:44am, Tony Papadimitriou wrote:
>>
>> So, please try this instead:
>>
>> sql xxx.db ".headers on" ".dump"
>
> sqlite> .headers on
> sqlite> CREATE TABLE xxx(`time zone`);
>
> On 8 Apr 2017, at 12:44am, Tony Papadimitriou wrote:
>
> So, please try this instead:
>
> sql xxx.db ".headers on" ".dump"
sqlite> .headers on
sqlite> CREATE TABLE xxx(`time zone`);
sqlite> insert into xxx values('1');
sqlite> .dump
PRAGMA foreign_keys=OFF;
BEGIN
-Original Message-
From: Simon Slavin
I notice that the command on those lines is "sql" rather than the "sqlite3"
I would expect. Tony, do you get the same error if you type those things
into the SQLite3 shell, rather than feeding them in using >your command
shell ? It works
On 7 Apr 2017, at 11:02pm, Richard Hipp wrote:
> On 4/7/17, Tony Papadimitriou wrote:
>> The following dump cannot be used to rebuild the database because the column
>> name is not properly quoted giving an error.
>>
>> To reproduce:
>>
>> sql xxx.db "CREATE
ist'
Subject: Re: [sqlite] Another .DUMP issue with v 3.18.0
Try using different quotes, not ones that have meaning to the shell.
--
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org]
On Beh
ril, 2017 17:04
> To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org>
> Subject: Re: [sqlite] Another .DUMP issue with v 3.18.0
>
> -Original Message-
> From: Josh Hunsaker
>
> >On Fri, Apr 7, 2017 at 3:02 PM, Richard Hipp wrote:
> >> O
-Original Message-
From: Josh Hunsaker
On Fri, Apr 7, 2017 at 3:02 PM, Richard Hipp wrote:
On 4/7/17, Tony Papadimitriou wrote:
sql xxx.db "CREATE TABLE xxx(`time zone`)" "insert into xxx values('1')"
sql .dump xxx.db | sql
I'm unable to repro.
Is this possibly because the
On Fri, Apr 7, 2017 at 3:02 PM, Richard Hipp wrote:
> On 4/7/17, Tony Papadimitriou wrote:
>>
>> sql xxx.db "CREATE TABLE xxx(`time zone`)" "insert into xxx values('1')"
>> sql .dump xxx.db | sql
>>
>
> I'm unable to repro.
>
Is this possibly because the shell that Tony is using is evaluating
On 4/7/17, Tony Papadimitriou wrote:
> The following dump cannot be used to rebuild the database because the column
> name is not properly quoted giving an error.
>
> To reproduce:
>
> sql xxx.db "CREATE TABLE xxx(`time zone`)" "insert into xxx values('1')"
> sql .dump xxx.db | sql
The following dump cannot be used to rebuild the database because the column
name is not properly quoted giving an error.
To reproduce:
sql xxx.db "CREATE TABLE xxx(`time zone`)" "insert into xxx values('1')"
sql .dump xxx.db | sql
Error: near line 4: near "zone": syntax error
On Thursday, 6 April, 2017 08:58, Dan Kennedy wrote:
> On 04/06/2017 08:26 PM, Keith Medcalf wrote:
> > Note the report first line. Interval is the primary key of both tables
> > so there is an internal index.
> Thanks for this. Should be fixed here:
>
That fixed the issue I was seeing the first time around, thanks.
Still getting some weirdness where it looks like the results are highly
dependent on the contents of sqlite_stat1. I've been trying to construct a
simplified version to share but am having trouble reproducing it on a smaller
On 04/06/2017 08:26 PM, Keith Medcalf wrote:
Note the report first line. Interval is the primary key of both tables so
there is an internal index.
Thanks for this. Should be fixed here:
http://www.sqlite.org/src/info/48826b222c110a90
Dan.
Table Forecast does the same but is not
Note the report first line. Interval is the primary key of both tables so
there is an internal index.
Table Forecast does the same but is not reported (because of the extra
unique constraints perhaps?)
The later two reported missing indexes are correct.
sqlite> .lint fkey-indexes
CREATE INDEX
* Dan Kennedy:
>> My concern is about sqlite3_step(UPDATE) without a following
>> sqlite3_reset(UPDATE). Perhaps I should change my wrapper to
>> unconditionally call sqlite3_reset() after DML-related sqlite3_step(),
>> whether the stepping operation succeeded or not.
>
> For a DML statement, I
On 11/11/2015 01:19 AM, Florian Weimer wrote:
> * Dan Kennedy:
>
>> On 10/18/2015 10:27 PM, Florian Weimer wrote:
>>> My first surprise was SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE (see
>>> ?SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE?). I have found another
>>> source of such snapshot failures
* Dan Kennedy:
> On 10/18/2015 10:27 PM, Florian Weimer wrote:
>> My first surprise was SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE (see
>> ?SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE?). I have found another
>> source of such snapshot failures with WAL-mode databases.
>>
>> I like to pre-compile my
On 10/18/2015 10:27 PM, Florian Weimer wrote:
> My first surprise was SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE (see
> ?SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE?). I have found another
> source of such snapshot failures with WAL-mode databases.
>
> I like to pre-compile my DML statements before
My first surprise was SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE (see
?SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE?). I have found another
source of such snapshot failures with WAL-mode databases.
I like to pre-compile my DML statements before starting transactions,
mainly for the implied syntax
you guys are flippin' gods ya know that right?
thanks!
On Jun 19, 2014, at 10:26 PM, Igor Tandetnik wrote:
> On 6/20/2014 1:20 AM, David M. Cotter wrote:
>> i want to delete from the table all records with plID = 1, but ONLY those
>> that have a corresponding record where
here's a table:
i want to delete from the table all records with plID = 1, but ONLY those that
have a corresponding record where plID == 851090 and where that record's soID
matches the one where plID = 1
so the query should delete rows 8-12, but leave 1-2 intact (and also leave 3-7)
there
On 2014/06/20 07:20, David M. Cotter wrote:
i want to delete from the table all records with plID = 1, but ONLY those that
have a corresponding record where plID == 851090 and where that record's soID
matches the one where plID = 1
so the query should delete rows 8-12, but leave 1-2 intact
you guys are flippin' gods ya know that right?
thanks!
On Jun 19, 2014, at 10:26 PM, Igor Tandetnik wrote:
> On 6/20/2014 1:20 AM, David M. Cotter wrote:
>> i want to delete from the table all records with plID = 1, but ONLY those
>> that have a corresponding record where
On 6/20/2014 1:20 AM, David M. Cotter wrote:
i want to delete from the table all records with plID = 1, but ONLY those that
have a corresponding record where plID == 851090 and where that record's soID
matches the one where plID = 1
delete from MyTable where plID = 1 and soID in (
select
> here's a table:
the list helpfully deletes enclosed pictures, even if they're wicked small..
here's the actual table:
http://karaoke.kjams.com/screenshots/table.png
___
sqlite-users mailing list
sqlite-users@sqlite.org
here's a table:
i want to delete from the table all records with plID = 1, but ONLY those that
have a corresponding record where plID == 851090 and where that record's soID
matches the one where plID = 1
so the query should delete rows 8-12, but leave 1-2 intact (and also leave 3-7)
there
http://www.sqlite.org/lockingv3.html , in section "5.0 Writing to a
database file", says:
"Future versions of SQLite might provide a "CHECKPOINT" SQL command
that will commit all changes made so far within a transaction but
retain the RESERVED lock so that additional changes can be made
without
http://www.sqlite.org/tempfiles.html , in section "2.7
Materializations Of Views And Subqueries", says:
"The rules for when a query and cannot be flattened are very complex
and are beyond the scope of this document. "
That should probably read, "...when a query _can_ and cannot be flattened...".
On Sat, 13 Jul 2013 00:09:36 -0600
"Keith Medcalf" wrote:
> UPDATE WHERE CURRENT OF CURSOR has been part of SQL since about, oh,
> 1969.
(I assume that's dramatic license.)
> Now then SQLite does not support the FOR UPDATE OF clause when
> defining a cursor (ie, doing a
> Richard Hipp said on Saturday, 13 July, 2013 11:59:
> > I don't know. It works entirely as expected. If I move a row (via
> > update) that I have already visited into a position where it is "yet
> > to be visited", then I will visit it twice -- both times exactly when
> > and where
On Sat, Jul 13, 2013 at 1:53 PM, Keith Medcalf wrote:
>
> I don't know. It works entirely as expected. If I move a row (via
> update) that I have already visited into a position where it is "yet to be
> visited", then I will visit it twice -- both times exactly when and
in wattage and
understanding.
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of Igor Tandetnik
> Sent: Saturday, 13 July, 2013 07:37
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Another 2 questio
On 7/13/2013 1:36 AM, Keith Medcalf wrote:
Of course, the behaviour is not actually "undefined" -- it is perfectly determinable and
entirely predictable and reasonable. However, if one does not understand the factors which
determine the behaviour then, for you, the behaviour is undefined. In
> It's not SQLite's "problem", I suppose. If it works as intended, it's
> not a bug. Where we disagree is over whether that intention best
> serves the application programmer.
> You think it's OK: he made his bed and now he can lie in it. Modify
> the table you haven't finished selecting,
> The major unexpected thing here is how SQLite deals with a case where
> two different connections (which may be from different apps on
> different computers) both have uncommitted changes. I think
> explaining things using this as the key point may make explaining the
> other aspects
rg] On Behalf Of Richard Hipp
> Sent: Friday, 12 July, 2013 14:03
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Another 2 questions about SQLite
>
> On Fri, Jul 12, 2013 at 3:01 PM, Igor Tandetnik <i...@tandetnik.org>
> wrote:
>
> > On 7/12
On Fri, 12 Jul 2013 14:25:36 -0400
Igor Tandetnik wrote:
> >it is very much SQLite's job to prevent logical
> > programming errors from corrupting the data.
>
> Define "the data". The database file remains perfectly intact, no
> corruption there. Your internal state might
On Fri, 12 Jul 2013 16:02:37 -0400
Richard Hipp wrote:
> On Fri, Jul 12, 2013 at 3:01 PM, Igor Tandetnik
> wrote:
>
> > On 7/12/2013 12:30 PM, James K. Lowden wrote:
> >
> >> The documented behavior is - if you modify the data as you iterate
> >>> over that
On 12 Jul 2013, at 9:02pm, Richard Hipp wrote:
> Proposed documentation enhancement here:
> http://www.sqlite.org/draft/isolation.html
I hope you don't mind that I posted this publicly. It's a bit strong for a
public forum, but I suspect that other readers of this forum
On Fri, Jul 12, 2013 at 3:01 PM, Igor Tandetnik wrote:
> On 7/12/2013 12:30 PM, James K. Lowden wrote:
>
>> The documented behavior is - if you modify the data as you iterate
>>> over that same data, the results are unpredictable.
>>>
>>
>> Where does it say that?
>>
>
> You
On 7/12/2013 12:30 PM, James K. Lowden wrote:
The documented behavior is - if you modify the data as you iterate
over that same data, the results are unpredictable.
Where does it say that?
You got me here. The behavior doesn't appear to be documented, and it
probably should. The closest I
On 7/12/2013 12:30 PM, James K. Lowden wrote:
On Mon, 08 Jul 2013 00:37:55 -0400
Igor Tandetnik wrote:
I don't believe it's SQLite's job to ensure the programmer doesn't
shoot herself in the foot. After all, you don't expect, say, the C++
compiler to prevent you from
Quoth "James K. Lowden" , on 2013-07-12 12:30:13
-0400:
> as the first one reads it. In fact, I'd be interested if you could
> point to a single standard C library function that, when called
> out-of-sequence, doesn't return an error but permits the process to
> proceed
On 12 Jul 2013, at 5:30pm, James K. Lowden wrote:
> There is no "SQLITE_OK_BUT_YOU_ARE_ON_YOUR_OWN" afaik.
This is the best idea ever. I vote it gets included in SQLite4.
Simon.
___
sqlite-users mailing list
On Mon, 08 Jul 2013 00:37:55 -0400
Igor Tandetnik wrote:
> I don't believe it's SQLite's job to ensure the programmer doesn't
> shoot herself in the foot. After all, you don't expect, say, the C++
> compiler to prevent you from destroying an object while another part
> of the
On 7/8/2013 12:09 AM, James K. Lowden wrote:
On Thu, 04 Jul 2013 16:08:38 -0400
Igor Tandetnik wrote:
On 7/4/2013 3:15 PM, James K. Lowden wrote:
This weird case is one of (I would say) misusing the connection.
IMO SQLite should return an error if prepare is issued on a
On 7/8/2013 12:09 AM, James K. Lowden wrote:
In real life, programs are complex, and libraries are misused
(intentionally or not). SQLite's job is to be a DBMS: to provide
predictable, safe access to the database, defending against errors
foreign and domestic (i.e. hardware errors, OS errors,
On Thu, 04 Jul 2013 16:08:38 -0400
Igor Tandetnik wrote:
> On 7/4/2013 3:15 PM, James K. Lowden wrote:
> > This weird case is one of (I would say) misusing the connection.
> > IMO SQLite should return an error if prepare is issued on a
> > connection for which a previous
On Thu, 4 Jul 2013 20:36:10 +0100
Simon Slavin wrote:
> On 4 Jul 2013, at 8:15pm, James K. Lowden
> wrote:
>
> > It doesn't usually matter, right? The fact that the atomic SELECT
> > is spread out across N function calls is irrelevant if they
On Thu, 4 Jul 2013 15:15:14 -0400, "James K. Lowden"
wrote:
> This weird case is one of (I would say) misusing the connection. IMO
> SQLite should return an error if prepare is issued on a connection for
> which a previous prepare was not finalized or reset. That
On 7/4/2013 3:15 PM, James K. Lowden wrote:
This weird case is one of (I would say) misusing the connection. IMO
SQLite should return an error if prepare is issued on a connection for
which a previous prepare was not finalized or reset. That would
forestall discussions like, this and prevent
On 7/4/2013 3:15 PM, James K. Lowden wrote:
If two processes sharing a connection...
This is a physical impossibility. There ain't no such thing as two
processes sharing a connection.
--
Igor Tandetnik
___
sqlite-users mailing list
On 4 Jul 2013, at 8:15pm, James K. Lowden wrote:
> It doesn't usually matter, right? The fact that the atomic SELECT is
> spread out across N function calls is irrelevant if they are executed
> in uninterrupted sequence, because other connections are blocked from
>
On Thu, Jul 4, 2013 at 9:15 PM, James K. Lowden wrote:
> On Mon, 01 Jul 2013 23:59:15 -0400
> Igor Tandetnik wrote:
>
> > > 2. Trying to re-use a single connection to issue a second query
> > > before finalizing the first one should return an error
On Tue, 2 Jul 2013 11:57:43 +0100
Simon Slavin wrote:
> The SELECT statement is fine and consistent. But the SELECT
> statement is all of _prepare(), _step(), and _finalize(). Igor is
> pointing out that that if you stop before _step() has returned
> SQLITE_DONE then you
On Mon, 01 Jul 2013 23:59:15 -0400
Igor Tandetnik wrote:
> > 2. Trying to re-use a single connection to issue a second query
> > before finalizing the first one should return an error
>
> No it should not, and does not. Try it.
>
> > because the library is being improperly
On 2 Jul 2013, at 3:33am, James K. Lowden wrote:
> Igor Tandetnik wrote:
>
>> On 6/30/2013 11:13 PM, Igor Korot wrote:
>>> Well I will use another statement variable as in the sample code.
>>> My questions was: if I call delete on the record that
On 7/1/2013 11:30 PM, James K. Lowden wrote:
Restricting ourselves to one process, I can think of two ways that
might go:
1. With two connections, one connection or the other will wait.
SELECT will return 0 or 10 rows.
Yes, between two connection, normal transaction isolation rules apply,
On Mon, 01 Jul 2013 23:00:27 -0400
Igor Tandetnik wrote:
> On 7/1/2013 10:33 PM, James K. Lowden wrote:
> > Igor Tandetnik wrote:
> >> If you change data that a live SELECT statement is iterating over,
> >> the outcome is unpredictable. It may appear to
On 7/1/2013 10:33 PM, James K. Lowden wrote:
On Sun, 30 Jun 2013 23:27:23 -0400
Igor Tandetnik wrote:
If you change data that a live SELECT statement is iterating over,
the outcome is unpredictable. It may appear to work, it may skip
rows, it may return some rows more than
On Sun, 30 Jun 2013 23:27:23 -0400
Igor Tandetnik wrote:
> On 6/30/2013 11:13 PM, Igor Korot wrote:
> > Well I will use another statement variable as in the sample code.
> > My questions was: if I call delete on the record that was just
> > retrieved in another query will
I wish.
I need to remove those records from another table as well. That's why I
need to retrieve playerid first.
So once again: will the delete affect the outer looping SQLite statement?
I hate to be the one asking the obvious questions, but why are you not using a trigger or or a foreign key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/06/13 20:17, Igor Korot wrote:
> Well I'm not familiar with SQLite internals, but one thing for sure:
> why go thru the process if you can avoid it?
You are trying to do premature optimization.
Note the "Lite" in the SQLite. It is already
On 6/30/2013 11:17 PM, Igor Korot wrote:
On Sun, Jun 30, 2013 at 7:47 PM, Igor Tandetnik wrote:
On 6/30/2013 10:27 PM, Igor Korot wrote:
1. I'm trying to minimize the number of requests I'm doing to the DB. What
I need is a way to count the number of rows that the query
On 1 Jul 2013, at 4:13am, Igor Korot wrote:
> Well I will use another statement variable as in the sample code.
> My questions was: if I call delete on the record that was just retrieved in
> another query will this delete affects it?
I can’t say a definite 'yes’ because it
On 6/30/2013 11:13 PM, Igor Korot wrote:
Well I will use another statement variable as in the sample code.
My questions was: if I call delete on the record that was just retrieved in
another query will this delete affects it?
If you change data that a live SELECT statement is iterating over,
On Sun, Jun 30, 2013 at 7:47 PM, Igor Tandetnik wrote:
> On 6/30/2013 10:27 PM, Igor Korot wrote:
>
>> 1. I'm trying to minimize the number of requests I'm doing to the DB. What
>> I need is a way to count the number of rows that the query return to me
>> prior to going thru
Simon,
On Sun, Jun 30, 2013 at 7:41 PM, Simon Slavin wrote:
>
> On 1 Jul 2013, at 3:27am, Igor Korot wrote:
>
> > 1. I'm trying to minimize the number of requests I'm doing to the DB.
> What
> > I need is a way to count the number of rows that the
On 6/30/2013 10:27 PM, Igor Korot wrote:
1. I'm trying to minimize the number of requests I'm doing to the DB. What
I need is a way to count the number of rows that the query return to me
prior to going thru the "sqlite3_step()".
If this number is 0, I want to skip the processing and just
On 1 Jul 2013, at 3:27am, Igor Korot wrote:
> 1. I'm trying to minimize the number of requests I'm doing to the DB. What
> I need is a way to count the number of rows that the query return to me
> prior to going thru the "sqlite3_step()".
Sorry, not possible. SQLite does
Hi, ALL,
1. I'm trying to minimize the number of requests I'm doing to the DB. What
I need is a way to count the number of rows that the query return to me
prior to going thru the "sqlite3_step()".
If this number is 0, I want to skip the processing and just return. It's
not an error situation, it
Seection 2.0 line 4
SQLite processes this by gather all the output of query and then running ...
SQLite processes this by gathering all the output of query and then running
...
A
^^^
___
sqlite-users
@Richard;
What kind of support are you supposed to be giving users? sqlite3.dll is a
DLL, not an application, and without looking at the source code, I know for
certain the DLL itself isn't asking someone to download something else,
ASSUMING of course, its a precompiled version from sqlite.org
It's not easy being an incon
On 4 December 2012 10:44, Richard Hipp wrote:
> Here is another example of the kind of email I get on a regular basis.
>
> Note that I also get phone calls about this. Sometimes at odd hours.
>
> -- Forwarded message --
> From: Åke
Here is another example of the kind of email I get on a regular basis.
Note that I also get phone calls about this. Sometimes at odd hours.
-- Forwarded message --
From: Åke Halvarson
Date: Tue, Dec 4, 2012 at 5:22 AM
Subject: sqlite.dll
To:
Dear Simon and Dan,
thanks for your valuable information, which we were looking for.
Kind regards
Alex
__
Od: "Simon Slavin"
Komu: General Discussion of SQLite Database
Datum: 21.01.2012 12:49
Předmět: Re: [sqlit
On 21 Jan 2012, at 8:28am, Dan Kennedy wrote:
> You can get the old behavior by issuing a statement like:
>
> PRAGMA page_size = 1024;
>
> When creating the database.
Alternatively, if that data is now fixed and you care about the filesize, do a
VACUUM
and see if that shrinks the database
On 01/21/2012 02:00 PM, Alexandr Němec wrote:
Dear all,
we have another question regarding the 3.7.10 version. We have a
database with cca 10 tables. After creating a new database in 3.7.10
and filling each table with about 10 - 100 data rows, we noticed that
the size of the database is 2x -
Dear all,
we have another question regarding the 3.7.10 version. We have a database with
cca 10 tables. After creating a new database in 3.7.10 and filling each table
with about 10 - 100 data rows, we noticed that the size of the database is 2x -
4x larger compared to 3.7.9 (using exact same
Not that you haven't had the debate before, but I hope this discussion
of my enhancement request for a raw flip() or reverse() function helps
to highlight some basic issues relating to Unicode in the database; I
don't mean to be beating any dead horses.
Roger Binns wrote:
My point was that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Romano wrote:
> The requirements for the flip() function I've requested are unambiguous:
> simply reverse the string, raw codepoint by codepoint.
My point was that your requirements are that, yet someone else wanting a
"flip" function could
Roger,
I have had a very brief time observing the SQLite community, the
opposite of your own experience, but I have been working with a variety
of databases since 1985: PICK, Revelation, FoxPro, Paradox, MS-Access,
Oracle, and SQLServer, among others. I'm not a newbie to databases but
am a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Romano wrote:
> I would hope that it could be included by default.
[Note I do not speak on behalf of the SQLite team but have been an observer
for many years]
Your request is extremely unlikely to go into the SQLite core as the bar is
*very*
Thanks for the heads-up, Jean-Denis.
I was going to try to deploy the almost-finished Flex/AIR app on my
wife's Mac notebook this weekend to see how it goes. That it works
quickly under Windows XP is all I know at this point. I am very
concerned about query performance and app
On 11/19/09 14:55 , "Tim Romano" wrote:
> The app was written in .NET against MS-Access; my Macintosh colleagues
> couldn't use it. They outnumbered the Windows users. But I didn't own a
> Mac and had never programmed on a Mac. But now Adobe Flex/AIR with
> SQLite is
Roger,
Also, you mentioned that it could take some time for a flip() function
to make its way into the OSX version assuming it had been accepted and
put on the docket.
I can wait a good long time for SQlite to add a flip() function. About
eight years ago now I wrote my app, a full-text search
Roger wrote:
... You still have the issue that the [flip()] code would likely be
excluded by default just as
soundex is, so it would still require re-compiling SQLite.
I would hope that it could be included by default. Those who are
concerned about the overall weight of the EXE (as a
Yet I don't want to do this reversal "in my application". I am not a C
programmer and would have to rely upon data-providers to talk to the
database. Providers, as good as they may be, are not 100% transparent
conduits between the client app and the database. Right now, three of
them are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Romano wrote:
> I respectfully disagree, Roger, about the simplicity. Creating an
> external DLL would complicate my distribution scenario significantly
> because I'll have just as many users of my little database application
> working with
On 18 Nov 2009, at 9:27pm, Roger Binns wrote:
> A C function of your choosing can be called on each new connection being
> created:[snip]
Thanks for your detailed answer.
Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
Tim Romano wrote:
> I respectfully disagree, Roger, about the simplicity. Creating an
> external DLL would complicate my distribution scenario significantly
> because I'll have just as many users of my little database
> application working with Apple OSX as with Windows.
Apologies. An accident -- I was trying to grab the To: address from a
previous email and didn't realize there was a big thing attached. I
don't see anything attached to this one. I hope there isn't.
Tim Romano
Jean-Christophe Deschamps wrote:
>
> Please don't set the ReplyTo field to the list
I respectfully disagree, Roger, about the simplicity. Creating an
external DLL would complicate my distribution scenario significantly
because I'll have just as many users of my little database application
working with Apple OSX as with Windows. I guarantee you, it would be
easier for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Slavin wrote:
> I googled, and there doesn't seem to be a page which describes the abilities
> and limitations the extension system has.
A C function of your choosing can be called on each new connection being
created:
On 18 Nov 2009, at 6:05pm, Roger Binns wrote:
> Tim Romano wrote:
>> This would be a convenient function to have. Are there technical
>> issues/obstacles?
>
> In general for all these feature requests for more functions there is no
> need for them to be added to the SQLite core. There is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Romano wrote:
> This would be a convenient function to have. Are there technical
> issues/obstacles?
In general for all these feature requests for more functions there is no
need for them to be added to the SQLite core. There is a very simple
> The blob (x'41' is a blob literal) is expected to contain a UTF-8 sequence, I
> believe.
I think it should be a database encoding which is either UTF-8 or
UTF-16. So for Tim's case if his database encoding is UTF-16 insert
statement can be like this:
insert test (id, myTextColumn) values(1,
1 - 100 of 153 matches
Mail list logo