Hello.
I have been having problems with page www.sqlite.org/contrib and I need file
extension-functions.c (50.96 KB) contributed by Liam Healy... There exist
some alternative place where can I download it?
Thanks.
--
«But Gwindor answered: 'The doom lies in yourself, not in your name.'»
JRR
Hello,
I'd like to be able to tell whether a SQLite database file has been updated
in any way. How would I go about implementing that?
I find about some file change counter but how i will get the value of file
change counter through C program
--
Akash Agrawal
On Sep 11, 2011, at 9:58 PM, Igor Tandetnik wrote:
> Mr. Puneet Kishor wrote:
>> geo table: 39K rows
>> id max_age min_age
>> --- ---
>> 1 Holocene Holocene
>> 5 Cambrian Silurian
>> 12 Cambrian Ordovician
>> 229 Cretaceous Quaternary
>>
>> intervals table:
To conclude on this topic, I figured out the usage of '_' .
--Original Message--
From: Igor Tandetnik
Sender: sqlite-users-boun...@sqlite.org
To: sqlite-users@sqlite.org
ReplyTo: General Discussion of SQLite Database
Subject: Re: [sqlite] Sqlite+ICU library and usage of LIKE
Sent: Sep
Mr. Puneet Kishor wrote:
> geo table: 39K rows
> id max_age min_age
> --- ---
> 1 Holocene Holocene
> 5 Cambrian Silurian
> 12 Cambrian Ordovician
> 229 Cretaceous Quaternary
>
> intervals table: ~450 rows
> id age_bottom age_top name color
> --- --
Apologies in advance for a terrible subject line -- I didn't know quite how to
phrase it better.
I have the following two tables (with sample data)
CREATE TABLE geo (
id INTEGER PRIMARY KEY,
max_age TEXT,
min_age TEXT
);
geo table: 39K rows
id max_age
On Sun, Sep 11, 2011 at 03:00:10PM +0100, Simon Slavin scratched on the wall:
> On 11 Sep 2011, at 2:49pm, Jay A. Kreibich wrote:
>
> >> I think that the 'OR REPLACE' clause refers to the primary key,
> >
> > No, it will trigger on any UNIQUE constraint violation.
> >
> > My guess is that one
Steffen Mangold wrote:
>
> It would really help me if you send me your step by step instructions.
> I had some experience with SVN, but it will help for building.
>
1. Download the Fossil binary for your platform (e.g. Windows):
On Sun, 11 Sep 2011 04:42:37 -0700 (PDT), liviodl
wrote:
>
>Hi guys,
>
>I'm trying to create a multi-column unique constraint in SQLite, but I don't
>have success. In table "players", I've created the following index:
>
>CREATE UNIQUE INDEX "players_unique" ON "players"
hi joe,
wow thanks for your fast help. Tomorrow I will try your patch.
It would really help me if you send me your step by step instructions.
I had some experience with SVN, but it will help for building.
Thank you!!
Steffen Mangold
Joe Mistachkin wrote:
>I believe that I've found and fixed
>
> Nothing changed, except now the SQLite 3 API *EXPLICITLY* says the
> text functions require either UTF-8 or UTF-16, but nothing stops
> someone doing the same as with SQLite2 and store it's text as BLOBs.
>
> I forgot to reply this. I thought about BLOB as it uses single byte storage
but
>
> Do you relly know that there is no 8859 encoding?
> The standards go from ISO-8859-1 to ISO-8859-16 and you would need to
> have collations for all of them and a way to let the user choose which
> one is the right one for them (including regional variations).
>
For me I just need the 8859-1.
>
> Possibly because SQLite3 supports UTF-8 and UTF-16 rather than ASCII.
> Assuming you're using the ICU stuff, of course.
>
Yes, I know that, but I wish to know the reason. Why the authors choose turn
off 8859 rather than keep both like as it was before? Technical reason?
> Exactly. Though
On Sun, Sep 11, 2011 at 15:55, Antonio Maniero wrote:
>>
>> I see. Well, SQLite2 is ancient: that ship has sailed and it's not coming
>> back.
>>
>> Did SQLite2 actually implement case-insensitive comparison on accented
>> Latin characters? I honestly don't know - by the time I
Simon Slavin wrote:
> Though I'm having trouble pointing to a page for the SQLite3 ICU stuff at the
> moment.
It would be here:
http://www.sqlite.org/cvstrac/fileview?f=sqlite/ext/icu/README.txt
but the server seems to be down at the moment.
--
Igor Tandetnik
Steffen Mangold wrote:
>
> I have a question to the System.Data.SQLite in action with the .Net
> TransactionScope. In the SQLite documentation is written that the
> default behavior of a transaction in case of an error is "ABORT".
> In documentation is also writen that "prior SQL statements
On 11 Sep 2011, at 3:55pm, Antonio Maniero wrote:
> Maybe someone else could say about the reason that SQLite dropped 8859
> encoding.
Possibly because SQLite3 supports UTF-8 and UTF-16 rather than ASCII. Assuming
you're using the ICU stuff, of course.
> I can use utf8 but for me SQLite
>
> I see. Well, SQLite2 is ancient: that ship has sailed and it's not coming
> back.
>
> Did SQLite2 actually implement case-insensitive comparison on accented
> Latin characters? I honestly don't know - by the time I got involved with
> SQLite (in late 2005), SQLite2 was already history, and its
Antonio Maniero wrote:
>>> Why SQLite dropped the 8859 or single byte support for text? Is there
>>> any technical reason?
>>
>> What do you mean, dropped? What exactly used to worked before and has
> stopped working now? What event has occurred between then and now that you
>
On 11 Sep 2011, at 2:49pm, Jay A. Kreibich wrote:
>> I think that the 'OR REPLACE' clause refers to the primary key,
>
> No, it will trigger on any UNIQUE constraint violation.
>
> My guess is that one of the individual columns has a UNIQUE constraint.
>
> Is "id" or one of the other
On Sun, Sep 11, 2011 at 02:00:48PM +0200, Bernd Lehmkuhl scratched on the wall:
> Am 11.09.2011 13:42, schrieb liviodl:
> >
> >I'm trying to create a multi-column unique constraint in SQLite, but I don't
> >have success. In table "players", I've created the following index:
> >
> > CREATE
Bernd Lehmkuhl wrote:
>
> I think that the 'OR REPLACE' clause refers to the primary key, which
> hasn't necessarily to do with a unique index defined elsewhere. So if
> you have a primary key set on id, that would be the result.
> ___
>
Am 11.09.2011 13:42, schrieb liviodl:
Hi guys,
I'm trying to create a multi-column unique constraint in SQLite, but I don't
have success. In table "players", I've created the following index:
CREATE UNIQUE INDEX "players_unique" ON "players" ("id" ASC, "skill"
ASC, "stagione" ASC,
> > Why SQLite dropped the 8859 or single byte support for text? Is there
> > any technical reason?
>
> What do you mean, dropped? What exactly used to worked before and has
stopped working now? What event has occurred between then and now that you
attribute the problem to?
Maybe I had
Hi guys,
I'm trying to create a multi-column unique constraint in SQLite, but I don't
have success. In table "players", I've created the following index:
CREATE UNIQUE INDEX "players_unique" ON "players" ("id" ASC, "skill"
ASC, "stagione" ASC, "settimana" ASC)
When I issue the following
On Sun, Sep 11, 2011 at 4:37 PM, Baruch Burstein wrote:
> Did you configure and make using the same options?
No, there is no such thing as configure on Windows. Both parser
"lemon" and compiler were run with the same options, as building using
"Makefile.msc" does this.
Did you configure and make using the same options?
On Sat, Sep 10, 2011 at 4:53 PM, Richard Tew wrote:
> Hi,
>
> Is it possible to get the library size down to 180 KB on Windows using
> Visual C++? I've also tried compiling for the a *nix based platform
> with gcc
27 matches
Mail list logo