Re: [sqlite] nVARCHAR as unique index

[Farzana]

Thanks for your reply Igor.

When we checked with the provided query we found that the duplicate values
are present in the BrandDescription. We are working with the device where
the memory is limited. We are suppose to sort the data by
BrandDescription.When we tried with "ORDER BY BrandDescription" in the query
to be executed, its taking more time than we expected.

Is there any work around to sort the data by BrandDescription physically?
Thanks in advance.

Regards,
Farzana.


Igor Tandetnik wrote:
> 
> "Farzana" <[EMAIL PROTECTED]>
> wrote in message news:[EMAIL PROTECTED]
>> We are using SQLite and we have the table structure as CREATE TABLE
>> Brand(PcNo numeric(4) Not Null,SubPcNo numeric(4) Not Null,BrandNo
>> numeric(9) Not Null,BrandDescription nVARCHAR(254)Not Null,ST
>> numeric(1),TS numeric(14)) where the index is CREATE UNIQUE index
>> BrandKey1 on Brand(PcNo,SubPcNo,BrandNo). When we use this table in
>> the application we are suppose to sort the datas by
>> BrandDescription.So we tried to create a unique index as CREATE
>> UNIQUE INDEX BrandKey2 on Brand(BrandDescription).But we couldn't
>> able to create the unique index.
> 
> Define "couldn't able". What exactly seems to be the problem? Did you 
> get an error message? What did the message say?
> 
> Is it possible that the values in BrandDescription column are not in 
> fact unique? If they are not, then naturally you would get an error 
> trying to create a unique index. Try this statement:
> 
> select * from Brand
> group by BrandDescription
> having count(*) > 1;
> 
> If this returns any rows, you have duplicates.
> 
> Igor Tandetnik 
> 
> 
> 
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/nVARCHAR-as-unique-index-tp17206197p17223665.html
Sent from the SQLite mailing list archive at Nabble.com.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Why is SQLite so slow across a network (afp Mac OS X)?

[Peter K. Stys]

Hi Folks:
I'm new to this list and just came across a major issue so I thought I'd
post here: I'm using SQLite (from REALbasic which uses the SQLite DB engine
for SQL support) to store image files, and while R/W to local files is
excellent, the same operations on files residing on a remote volume mounted
via afp or smb (all Mac OS X) suffer a 20-fold performance hit.

Why is this, and is there a workaround?

To be clear, while the remote files are on a server, this is still single
user access to a single file at a time, just remotely.

Any input greatly appreciated!

Peter.


-- 
-
Peter K. Stys, MD
Dept. of Clinical Neurosciences
Hotchkiss Brain Institute
University of Calgary
tel (403) 210-8646
-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Help!!! sqlite 3.5.8 crash: access violation

[qinligeng]

When I execute sql statement "delete from Carimages where OpTime <'2008-05-01 
00:00:00'"  in my database, sqlite3 crashed.
The Exception Information reported by XP is:
Code: 0xc005   Flags:0x  
Record: 0x   Address: 0x00406652

The sqlite3.exe is downloaded from http://www.sqlite.org/sqlite-3_5_8.zip
The database file is to big ( about 600M, after compressed by WinRAR, the size 
is 18M), so I can't upload here.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Proposed SQLite C/C++ interface behavior change.

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Virgilio Alexandre Fornazin wrote:
> A good and new safe could be a sqlite3_close_v2() call prototyped like
> 
> int sqlite3_close_v2(sqlite3 * db, int closePendingStatements);

Funnily enough that is exactly what I provide in my Python wrapper for
SQLite!  Reference counting ensures that the sqlite3_db can't be freed
before all the statements are closed but the above method is a quick way
for the developer to proactively close everything.

Having a close_v2 is most likely the best solution since there won't be
semantics changes over what people have already developed.  It can also
ensure the right thing happens when threads are being abused.

Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIKlSymOOfHg372QQRAiEbAJ9mbFpensXkTXmJtI90vPfTqMNpswCgmh2/
2HwZvkW8FdDUzWId2mtE5fs=
=oawA
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Proposed SQLite C/C++ interface behavior change.

[Virgilio Alexandre Fornazin]

A good and new safe could be a sqlite3_close_v2() call prototyped like

int sqlite3_close_v2(sqlite3 * db, int closePendingStatements);

and current sqlite3_close() call could become

int sqlite3_close(sqlite3 * db)
{
return sqlite3_close_v2(db, 0);
}

In this way, current running code does not need to be changed, and
developers that use v2 interface with close = 1 are aware of what
they are doing.

This not only mantains backward compatibility but also give more
control of sqlite behaviour.
 
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of D. Richard Hipp
Sent: terça-feira, 13 de maio de 2008 20:51
To: General Discussion of SQLite Database
Subject: [sqlite] Proposed SQLite C/C++ interface behavior change.

The currently documented behavior of sqlite3_close() is that  when it  
called on a database connection that has unfinalized prepared  
statements is to return SQLITE_BUSY and fail to close the connection.   
The rational is that we did not want a call to sqlite3_close() to  
destroy sqlite3_stmt* pointers out from under other subsystems.  But  
for version 3.6.0 we are considering a behavior change in which a call  
to sqlite3_close() will silently and automatically call  
sqlite3_finalize() on all outstanding prepared statements.

This is, technically, an incompatible change and we strive to avoid  
incompatible changes. But we think it unlikely that this change will  
cause any problems, and in fact we suspect it will likely fix more  
bugs than it will induce.  But before we move forward, it seems good  
to submit the idea to the community of SQLite users and programmers.

Does anybody have any thoughts on this proposed behavior changes for  
the sqlite3_close() interface?

D. Richard Hipp
[EMAIL PROTECTED]

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Proposed SQLite C/C++ interface behavior change.

[Richard Klein]

> Does anybody have any thoughts on this proposed behavior changes for  
> the sqlite3_close() interface?
> 
> D. Richard Hipp
> [EMAIL PROTECTED]

Fine with me.

- Richard Klein

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Proposed SQLite C/C++ interface behavior change.

[Scott Hess]

On Tue, May 13, 2008 at 4:51 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> The currently documented behavior of sqlite3_close() is that when it
> called on a database connection that has unfinalized prepared
> statements is to return SQLITE_BUSY and fail to close the connection.
> The rational is that we did not want a call to sqlite3_close() to
> destroy sqlite3_stmt* pointers out from under other subsystems. But
> for version 3.6.0 we are considering a behavior change in which a call
> to sqlite3_close() will silently and automatically call
> sqlite3_finalize() on all outstanding prepared statements.
>
> This is, technically, an incompatible change and we strive to avoid
> incompatible changes. But we think it unlikely that this change will
> cause any problems, and in fact we suspect it will likely fix more
> bugs than it will induce. But before we move forward, it seems good
> to submit the idea to the community of SQLite users and programmers.
>
> Does anybody have any thoughts on this proposed behavior changes for
> the sqlite3_close() interface?

What will happen if you call things like this:

db = sqlite3_open(...);
sqlite3_prepare_v2(db, zSql, -1, , NULL);
// ...
sqlite3_close(db);
sqlite3_finalize(stmt);

??? If sqlite3_finalize() will succeed, then this seems pretty reasonable to 
me. If sqlite3_finalize() will fail with a segfault or somesuch, that may be 
dangerous.

My rational is that if someone is building a system which is abstracting 
SQLite, then it may be that the database handles and the statement handles 
will not have clear clean-up ordering (for instance in a garbage-collected 
system). One _could_ go ahead and create such an ordering by using 
refcounting or whatever is appropriate in your system, but it would also 
seem reasonable for SQLite to manage this.

This may also come up with multi-threaded systems, where it could be 
challenging to convince another thread to finalize statements before calling 
close.

I don't suggest that you should be able to do anything interesting with the 
orphaned statement handle at this point, other than finalizing it. I suppose 
it would be nice if all statement-handle functions would start throwing 
SQLITE_MISUSE or other appropriate error code.

-scott
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Proposed SQLite C/C++ interface behavior change.

[D. Richard Hipp]

The currently documented behavior of sqlite3_close() is that  when it  
called on a database connection that has unfinalized prepared  
statements is to return SQLITE_BUSY and fail to close the connection.   
The rational is that we did not want a call to sqlite3_close() to  
destroy sqlite3_stmt* pointers out from under other subsystems.  But  
for version 3.6.0 we are considering a behavior change in which a call  
to sqlite3_close() will silently and automatically call  
sqlite3_finalize() on all outstanding prepared statements.

This is, technically, an incompatible change and we strive to avoid  
incompatible changes. But we think it unlikely that this change will  
cause any problems, and in fact we suspect it will likely fix more  
bugs than it will induce.  But before we move forward, it seems good  
to submit the idea to the community of SQLite users and programmers.

Does anybody have any thoughts on this proposed behavior changes for  
the sqlite3_close() interface?

D. Richard Hipp
[EMAIL PROTECTED]

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Undo logs and transactions

[David Barrett]

Yes, I completely agree.  But a single "undoable event" generates 
multiple changes to the database (which might as well be done inside a 
single transaction).  Thus one click on Undo results in multiple changes 
to undo the event (ie, undoing the entire event's transaction).  This 
implies that somehow the undo log either:

- Tags multiple rows in the undo log as comprising a single event, or
- Accumulates multiple queries into a single row in the undo log

I really liked the elegance of using triggers to automatically create 
the undo log, but I don't see how to accomplish either of the above 
strategies (tagging a group of undo rows, or concatenating multiple 
undos into a single row) in that design without some manual legwork.

So my question was whether there is some "COMMIT_COUNT()" SQL function 
or constant that represents "the number of committed transactions on 
this database", as then I could just stick that in the trigger query and 
insert it along with the undo query into the undo log as follows:

CREATE TEMP TRIGGER _ex1_it AFTER INSERT ON ex1 BEGIN
INSERT INTO undolog VALUES(NULL,COMMIT_COUNT(),'DELETE FROM ex1 WHERE 
rowid='||new.rowid);
END;

Then multiple INSERTs in a single transaction would generate multiple 
DELETEs in the undolog, all tagged with the same commit count.  Later, I 
could look up the set of queries necessary to undo that transaction with:

SELECT sql FROM undolog WHERE commitcount=XXX;

The upshot is I could roll back one transaction at a time, all the way 
back to the beginning (or as far as the undo log goes).

But lacking a COMMIT_COUNT() function, I might instead just create a 
simple table:

CREATE TABLE commitcount(num)

And then increment that at the start of each transaction:

UPDATE commitcount SET num=(SELECT num FROM commitcount)+1;

And then my trigger could be something like:

CREATE TEMP TRIGGER _ex1_it AFTER INSERT ON ex1 BEGIN
INSERT INTO undolog VALUES(NULL,(SELECT num FROM commitcount),'DELETE 
FROM ex1 WHERE rowid='||new.rowid);
END;

This'll do the same thing, but requires a subquery, an extra table, and 
manual incrementing of the commit count.  Works, but is yucky.

Another way might be to create a table that just keeps track of which 
range in the undolog corresponds to which distinct undoable event (aka 
transaction)... Perhaps a bit cleaner, but still not great.

Anyway, I was just curious if the COMMIT_COUNT() function existed, 
because then it'd be really clean and easy.  But it sounds it doesn't, 
and that's what I wanted to know.  Thanks!

-david

D. Richard Hipp wrote:
> On May 13, 2008, at 6:21 PM, David Barrett wrote:
> 
>> True, but even an application would need to "undo" in transactions,  
>> I'd
>> think.  Like, if a user drags a widget from column A to B, it  
>> generates
>> an INSERT in one column and a DELETE in another.  Pressing Undo once
>> would leave it in both columns, which is probably unexpected.
>>
> 
> And undo/redo mechanism typically groups actions together by user  
> input event.  The application is typically event driven.  It sits idle  
> waiting for a user event, such as a mouse click.  That event might  
> trigger a cascade of related events, some of which involve database  
> changes.  All database changes associated with that one event are  
> undone together.  You know that you have reached the end of your event  
> cascade when the event loop goes idle again.
> 
> For processing gestures (drags, and other inputs that involve multiple  
> events spread out over time) you acquire a lock or a "grab" at the  
> beginning of the gesture, hold it throughout the gesture, then release  
> it when the gesture completes.  You do not finish the undo package  
> until the end of the gesture.  So the complete rule for when you stop  
> one undoable entry and start a new one is: you are idle (no pending  
> events) and you are not holding a grab.
> 
> D. Richard Hipp
> [EMAIL PROTECTED]
> 
> 
> 
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Undo logs and transactions

[David Barrett]

True, but even an application would need to "undo" in transactions, I'd 
think.  Like, if a user drags a widget from column A to B, it generates 
an INSERT in one column and a DELETE in another.  Pressing Undo once 
would leave it in both columns, which is probably unexpected.

Anyway, I was more thinking of a "transaction count" sort of variable, 
indicating how many total transactions have been committed to the 
database.  Just something to group undo log entries by transaction 
without maintaining a manual transaction identifier.

Thanks for considering it!

-david

Ken wrote:
> the Undo/Redo mechanism described is not really for transactions but rather a 
> "Button" within an application. So that the user can undo/redo changes.
> 
> Only one transaction can be active at a time. So to the best of my knowledge 
> there is no "transaction number" as there can be only 1. Now you may go ahead 
> and implement "pseudo transactions" and implement your own transaction 
> number.  etc...
> 
> HTH,
> Ken
> 
> 
> David Barrett <[EMAIL PROTECTED]> wrote: What's the best way to group undo 
> log entries by transaction?  Is there 
> a function that returns the current transaction number?  Or what's the 
> best way to set a global variable that is inserted into the undo log by 
> the trigger?
> 
> As background, the wiki has a great page on undo/redo:
> 
>  http://www.sqlite.org/cvstrac/wiki?p=UndoRedo
> 
> But unless I misunderstand, it seems that a single transaction will 
> create multiple entries in the log.  For example, a transaction 
> containing both an insert and a delete will generate two entries in the 
> undo log.  Therefore, to undo that transaction, I need to atomically 
> commit the "undo" of both the insert and delete in a single transaction.
> 
> That's fine, but the log created by the example doesn't seem to indicate 
> which group of undo rows correspond to a single transaction.  Indeed, 
> the word "transaction" doesn't even appear in the page.
> 
> Now, digging through the archives I see reference to a "transaction 
> number" here:
> 
> http://www.mail-archive.com/sqlite-users@sqlite.org/msg23962.html
> 
> Is there any explicit way to get the current transaction number?  I was 
> hoping to see some "transaction_number()" function here, but I don't:
> 
>  http://www.sqlite.org/lang_corefunc.html
> 
> If such a function did exist, then I could just update the triggers to 
> insert that along with the corresponding SQL.
> 
> Lacking that, what's the best way to manually to set some kind of global 
> variable at the start of each transaction?  One way is to maintain a 
> separate table with a single cell containing the latest transaction 
> number (which I manually increment at the start of each transaction) and 
> then just SELECT that in the trigger sub-query, but that seems yucky. 
> Is there an easier way I'm missing?
> 
> Thanks!
> 
> -david
> 
> 
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> 
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Undo logs and transactions

[Ken]

the Undo/Redo mechanism described is not really for transactions but rather a 
"Button" within an application. So that the user can undo/redo changes.

Only one transaction can be active at a time. So to the best of my knowledge 
there is no "transaction number" as there can be only 1. Now you may go ahead 
and implement "pseudo transactions" and implement your own transaction number.  
etc...

HTH,
Ken


David Barrett <[EMAIL PROTECTED]> wrote: What's the best way to group undo log 
entries by transaction?  Is there 
a function that returns the current transaction number?  Or what's the 
best way to set a global variable that is inserted into the undo log by 
the trigger?

As background, the wiki has a great page on undo/redo:

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

But unless I misunderstand, it seems that a single transaction will 
create multiple entries in the log.  For example, a transaction 
containing both an insert and a delete will generate two entries in the 
undo log.  Therefore, to undo that transaction, I need to atomically 
commit the "undo" of both the insert and delete in a single transaction.

That's fine, but the log created by the example doesn't seem to indicate 
which group of undo rows correspond to a single transaction.  Indeed, 
the word "transaction" doesn't even appear in the page.

Now, digging through the archives I see reference to a "transaction 
number" here:

http://www.mail-archive.com/sqlite-users@sqlite.org/msg23962.html

Is there any explicit way to get the current transaction number?  I was 
hoping to see some "transaction_number()" function here, but I don't:

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

If such a function did exist, then I could just update the triggers to 
insert that along with the corresponding SQL.

Lacking that, what's the best way to manually to set some kind of global 
variable at the start of each transaction?  One way is to maintain a 
separate table with a single cell containing the latest transaction 
number (which I manually increment at the start of each transaction) and 
then just SELECT that in the trigger sub-query, but that seems yucky. 
Is there an easier way I'm missing?

Thanks!

-david


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Mailing list

[Rich Shepard]

On Tue, 13 May 2008, Darren Duncan wrote:

> Email lists have several important advantages over typical web boards, as I
> see it:
>
> 1.  All the discussion details come to my email box that I regularly
> check, so I can be aware of and respond to things quickly if I choose.  By
> contrast with a web board, I'd have to go out of my way to remember to
> periodically check in with the board to see if anything interesting came
> up, and often I would forget to do so.  This all said, it is very useful
> to see web archives of the email lists to browse.

Darren,

   If I may recast the above to a simpler form, we can say that with mail
lists the information is pushed to you. With web-based fora you have to
explicitly go there and pull the information to you.

   For many of us who are very busy and subscribe to a number of pertinent
mail lists, it's much more efficient to have the messages come in and be
sorted into the appropriate file by procmail recipes than it is to
explicitly visit each web site, log onto the forum, then go look for
messages of interest.

Rich

-- 
Richard B. Shepard, Ph.D.   |  IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
 Voice: 503-667-4517  Fax: 503-667-8863
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Porting into a microcontroller, minimum requirements

[Dennis Jenkins]

Jay A. Kreibich wrote:
> On Wed, May 07, 2008 at 10:25:49PM -0400, Andrew Cunningham scratched on the 
> wall:
>
>   
>> "I have doubts that you will be able to get SQLite to work on anything
>> less than a 32-bit processor.
>> D. Richard Hipp"
>> 
>
>   
>> I was under the impression as long as the processor had enough room to
>> hold the program (and RAM) it would work.
>> 
>
>   Yeah, but you have to compile it first...
>
>   
>> The difference I would have
>> expected would simply be speed of execution, but eventually getting
>> there.  With simple inserts/queries and the speed of sqlite, I thought
>> it should be okay.
>> 
>
>   I suspect the issue has to do with 64-bit integer support.  SQLite does
>   a lot with native 64-bit integer values (e.g. "unsigned long long int").
>   Most 32-bit processors have instructions that can deal with 64 bit
>   values as single, whole values, even if they require a lot of
>   slight-of-hand behind the scenes.  Even if the processor doesn't have
>   explicit instructions, the compiler can often fake it by using the 
>   overflow bits and a lot of byte shuffling.
>
>   I suppose it would be possible to play the same games with a 16 bit
>   (or even 8) processor, but I'm guessing the compilers for most of
>   these smaller chips don't support long long ints.  Even if they do,
>   it is going to be pretty slow and inflate the code side.
>
> -j
>
>   

I once thought about trying to compile it with "cc65" to run on an 
Apple IIe, for fun.  I then calculated that the Apple II doesn't have 
enough RAM in a flat address space.  I then decided that I'd rather go 
outside and enjoy the sunshine. :)

However... I still wonder if it would be possible.  Maybe if the 
compile could automatically split the code into sections that could work 
like "overlays" did back in the Borland C/Pascal days on MS-DOS.  But I 
suspect that memory access would be a problem

I could also compile Sqlite into MIPS R2000, and write a small 
emulator to run on the Apple (that transparently handled bank-switching 
and paging RAM).  That might work.  Slowly...


-- 
CONFIDENTIALITY NOTICE
This electronic mail and the information contained herein are intended for the 
named recipient only.  It may contain confidential, proprietary and/or 
privileged information.  If you have received this electronic mail in error, 
please do not read any text other than the text of this notice and do not open 
any attachments. Also, please immediately notify the sender by replying to this 
electronic mail or by collect call to (262) 796-0925. After notifying the 
sender as described above, please delete this electronic mail message 
immediately and purge the item from the deleted items folder (or the 
equivalent) of your electronic mail system. Thank you.

--

The above email disclaimer is required by our legal department.  However, if 
you would like a more humorous disclaimer, check here: 
http://www-users.cs.york.ac.uk/susan/joke/disclaim.htm


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Mailing list

[Darren Duncan]

[EMAIL PROTECTED] wrote:
> I apologize if this is off topic but wouldn't it be better to use some 
> standard discussion board, like PHPBB  instead of mailing list? It is pain to 
> use mailing lists (you have couple of them for sqlite), ((un)registration, 
> posting, receiving tons of e-mails, searching, etc.).
> Message from my other free email was rejected because of it's IP was listed 
> at some spam list. I think mailing lists worked fine 20 years ago but does it 
> have any advantage today ? :)
> Rado

Email lists have several important advantages over typical web boards, as I 
see it:

1.  All the discussion details come to my email box that I regularly check, 
so I can be aware of and respond to things quickly if I choose.  By 
contrast with a web board, I'd have to go out of my way to remember to 
periodically check in with the board to see if anything interesting came 
up, and often I would forget to do so.  This all said, it is very useful to 
see web archives of the email lists to browse.

2.  With email lists, its easy to have a local archive of the list, at 
least if one downloads their emails to their computers, so our records stay 
and are searchable if the list disappears or the internet goes off.

3.  Email programs are typically easier to use, and are more reliable.

I may have missed some points.

This all said, I recognize some advantages of BBs over email.

I think the best option is a hybrid.  Have some database-backed system with 
both a web interface and an email interface, and people can choose to 
connect one or both ways.  Any messages posted on the web interface go to 
the email users, and vice-versa.  Then you have both a web archive of 
everything, and local users can have their own archive too.

Perhaps more specifically I suggest a hybrid of what things like Yahoo 
Groups provides, and a bulletin board.  But I don't know if those tools 
exist yet.

-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] sqlite3_transfer_bindings obsolete?

[Shawn Wilsher]

We most certainly are using sqlite3_prepare_v2.  This use case is a
bit more exotic.

We are currently working on an async database access API (discussion
thread [1]).  The idea is to have a user prepare and bind parameters
on the calling thread, then clone that statement to send it to the
background thread that will process the results.  Since a statement
object can only be accessed on one thread at a time (at least that's
my understanding of it), the original statement is still usable on the
calling thread (and could be used again immediately even if the other
thread is doing work).

Cheers,

Shawn

[1] 
http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/045fed0ecba487cc

On Tue, May 13, 2008 at 2:18 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
>
> On May 13, 2008, at 2:05 PM, Shawn Wilsher wrote:
>
>> I was looking through the documentation and was wondering why
>> sqlite3_transfer_bindings has been marked as obsolete.  It's something
>> that we use currently in our code, and I was looking to use it again
>> for something new.  Is there a new way to accomplish the same thing
>> that this function does?  What was the rational for removing it.
>>
>> If you need a use case for why Mozilla needs it, I'd be happy to
>> oblige.
>>
>
>
> We strive to avoid incompatibilities.  So even though
> sqlite3_transfer_bindings() is marked as obsolete, that just means (in
> the words of the documentation) that we are not going to tell you want
> it does.  :-)  It isn't going away.  There are tests in the test suite
> to make sure it works.
>
> sqlite3_transfer_bindings() was intended for use with
> sqlite3_prepare() when sqlite3_step() returns SQLITE_SCHEMA.  After
> the schema error, one creates a new prepared statement from the
> original SQL, uses sqlite3_transfer_bindings() to move the bindings
> from the old prepared statement to the new, finalizes the old prepared
> statement, then retries with the new prepared statement.  But all of
> that was made obsolete by sqlite3_prepare_v2().  Sqlite3_prepare_v2(),
> you will recall, handles the SQLITE_SCHEMA errors automatically so the
> use of sqlite3_transfer_bindings() is no longer required.
>
> I am curious to know what alternative use Mozilla has found for
> sqlite3_transfer_bindings(), though.  You are using
> sqlite3_prepare_v2() in place of sqlite3_prepare() I trust.  You
> should be if you are not since applications that use
> sqlite3_prepare_v2() are less prone to bugs in error handling logic
> (by virtue of the fact that they can essentially ignore SQLITE_SCHEMA).
>
> D. Richard Hipp
> [EMAIL PROTECTED]
>
>
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] sqlite3_transfer_bindings obsolete?

[D. Richard Hipp]

On May 13, 2008, at 2:05 PM, Shawn Wilsher wrote:

> I was looking through the documentation and was wondering why
> sqlite3_transfer_bindings has been marked as obsolete.  It's something
> that we use currently in our code, and I was looking to use it again
> for something new.  Is there a new way to accomplish the same thing
> that this function does?  What was the rational for removing it.
>
> If you need a use case for why Mozilla needs it, I'd be happy to  
> oblige.
>


We strive to avoid incompatibilities.  So even though  
sqlite3_transfer_bindings() is marked as obsolete, that just means (in  
the words of the documentation) that we are not going to tell you want  
it does.  :-)  It isn't going away.  There are tests in the test suite  
to make sure it works.

sqlite3_transfer_bindings() was intended for use with  
sqlite3_prepare() when sqlite3_step() returns SQLITE_SCHEMA.  After  
the schema error, one creates a new prepared statement from the  
original SQL, uses sqlite3_transfer_bindings() to move the bindings  
from the old prepared statement to the new, finalizes the old prepared  
statement, then retries with the new prepared statement.  But all of  
that was made obsolete by sqlite3_prepare_v2().  Sqlite3_prepare_v2(),  
you will recall, handles the SQLITE_SCHEMA errors automatically so the  
use of sqlite3_transfer_bindings() is no longer required.

I am curious to know what alternative use Mozilla has found for  
sqlite3_transfer_bindings(), though.  You are using  
sqlite3_prepare_v2() in place of sqlite3_prepare() I trust.  You  
should be if you are not since applications that use  
sqlite3_prepare_v2() are less prone to bugs in error handling logic  
(by virtue of the fact that they can essentially ignore SQLITE_SCHEMA).

D. Richard Hipp
[EMAIL PROTECTED]



___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] sqlite3_transfer_bindings obsolete?

[Shawn Wilsher]

I was looking through the documentation and was wondering why
sqlite3_transfer_bindings has been marked as obsolete.  It's something
that we use currently in our code, and I was looking to use it again
for something new.  Is there a new way to accomplish the same thing
that this function does?  What was the rational for removing it.

If you need a use case for why Mozilla needs it, I'd be happy to oblige.

Cheers,

Shawn Wilsher
Mozilla Developer
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Precompiled AIX Version?

[John Stanton]

You shouldn't need to link.  You could just compile it into your 
application.

Derek Lee-Wo wrote:
>> If you do not use configure you have less control over compile options.  You
>> need to think about whether yiou need to compile it thread safe or not.
> 
> The app is single threaded so I don't need a thread-safe version.  I
> think for my immediate needs, I should be OK just linking in the
> sqlite3.c file.
> 
> Derek
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Precompiled AIX Version?

[Derek Lee-Wo]

> If you do not use configure you have less control over compile options.  You
> need to think about whether yiou need to compile it thread safe or not.

The app is single threaded so I don't need a thread-safe version.  I
think for my immediate needs, I should be OK just linking in the
sqlite3.c file.

Derek
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compatibility problems with sqlite3 and On-Time RTOS

[Luiz Azevedo]

Does anyone run sqlite3 in an OnTime real time operating system?

Luiz Azevedo
Daiken Ltd


AVISO LEGAL
Esta mensagem é exclusivamente para a pessoa a quem se destina e pode conter 
informações confidenciais ou legalmente protegidas. A transmissão incorreta da 
mensagem não acarreta a perda de seu caráter confidencial. Caso ela tenha sido 
recebida por engano, solicitamos que seja devolvida ao remetente e apagada de 
seu sistema imediatamente. É vedado, a qualquer pessoa que não seja 
destinatário, usar, revelar, distribuir ou copiar qualquer parte desta mensagem.

DISCLAIMER
This message is destined exclusively to the intendend receiver. It may contain 
confidential or legally protected information. The incorrect transmission of 
this message does not mean the loss of its confidentiality. If this message is 
receiveid by mistake, please send it back to the sender and delete it from your 
system immediately. It is forbidden to any person who is not intendend receiver 
to use, reveal, distribute, or copy any part if this message.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Precompiled AIX Version?

[John Stanton]

If you do not use configure you have less control over compile options. 
  You need to think about whether yiou need to compile it thread safe or 
not.

Derek Lee-Wo wrote:
> AIX 5.3 and I tried both xlC and gcc, but if I had a choice, I would
>  prefer to use xlC.
> 
>  I decided to simply try linking in sqlite3.c (from the amalgamated
>  distribution) to my app and it "seems" to be working.  I haven't done
>  much other than create a datafile and a table, but so far it's
>  working.
> 
>  Do you think I can continue to operate that way, or it really
>  recommended that I get the configure/make working correctly?
> 
> 
> 
> 
> 
> 
>  On Tue, May 13, 2008 at 11:05 AM, John Stanton <[EMAIL PROTECTED]> wrote:
>  > What verion of AIX are you using?  What compiler?  gcc or xlC?
>  >  JS
>  >
>  >  Derek Lee-Wo wrote:
>  >
>  > >
>  > >
>  > >
>  > > Is there a precompiled version of sqlite3 available for AIX?  I did a
>  > > Google search, but can't find anything.
>  > >
>  > > I would build it myself, but I'm having a really hard time as the
>  > > configure script wouldn't run fully.  First it complains about grep,
>  > > even when I installed the GNU grep, but I hacked configure to get
>  > > around that and then it complained about not finding a suitable
>  > > linker.  I did set CC to be both gcc and cc.
>  > >
>  > > At this point I would be happy to find a precompiled static sqlite3
>  > library
>  > > ___
>  > > sqlite-users mailing list
>  > > sqlite-users@sqlite.org
>  > > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>  > >
>  >
>  >
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Precompiled AIX Version?

[Derek Lee-Wo]

AIX 5.3 and I tried both xlC and gcc, but if I had a choice, I would
 prefer to use xlC.

 I decided to simply try linking in sqlite3.c (from the amalgamated
 distribution) to my app and it "seems" to be working.  I haven't done
 much other than create a datafile and a table, but so far it's
 working.

 Do you think I can continue to operate that way, or it really
 recommended that I get the configure/make working correctly?






 On Tue, May 13, 2008 at 11:05 AM, John Stanton <[EMAIL PROTECTED]> wrote:
 > What verion of AIX are you using?  What compiler?  gcc or xlC?
 >  JS
 >
 >  Derek Lee-Wo wrote:
 >
 > >
 > >
 > >
 > > Is there a precompiled version of sqlite3 available for AIX?  I did a
 > > Google search, but can't find anything.
 > >
 > > I would build it myself, but I'm having a really hard time as the
 > > configure script wouldn't run fully.  First it complains about grep,
 > > even when I installed the GNU grep, but I hacked configure to get
 > > around that and then it complained about not finding a suitable
 > > linker.  I did set CC to be both gcc and cc.
 > >
 > > At this point I would be happy to find a precompiled static sqlite3
 > library
 > > ___
 > > sqlite-users mailing list
 > > sqlite-users@sqlite.org
 > > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
 > >
 >
 >
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Precompiled AIX Version?

[John Stanton]

What verion of AIX are you using?  What compiler?  gcc or xlC?
JS

Derek Lee-Wo wrote:
> Is there a precompiled version of sqlite3 available for AIX?  I did a
> Google search, but can't find anything.
> 
> I would build it myself, but I'm having a really hard time as the
> configure script wouldn't run fully.  First it complains about grep,
> even when I installed the GNU grep, but I hacked configure to get
> around that and then it complained about not finding a suitable
> linker.  I did set CC to be both gcc and cc.
> 
> At this point I would be happy to find a precompiled static sqlite3 library
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Distributed transaction best practices

[John Stanton]

We implement a distributed synchronized Sqlite database by queueing 
changes.  In our case it is designed to permit internet operation to 
continue during network failures or congestion.

Virgilio Alexandre Fornazin wrote:
> The best you can do actually with SQLite is a 'mirror-replicating' mode
> engine
> that works like Microsoft Windows Active Directory Database, to build a king
> of 
> High Availability / Load Balancing server.
> 
> You have a farm of servers (or workstations, etc) receiving SQL commands by
> a 
> channel (socket, pipe, whatever). They force a 'election' do decide what´s
> the
> best servers to become master, then they agree on that and transactions (all
> 
> commands that modify the database) are first applied to the master server
> then
> 'mirrored' to slave servers. In this design, if a 'child' server cannot
> complete
> the transaction that are completed by master and any other server, there is
> a
> critical problem in that slave node, and you must consider it offline or
> some kind of state that you need to check if by hand or by one tool you
> might
> develop for this. In this scenario, you can do a 'load balance' in SELECT´s,
> distributing querying belong all servers, creating affinities for tables, 
> buffering most used tables in a memory database, etc.
> 
> I´m currently implementing services for finantial stock exchanging services
> that
> works in the way I told you, if you are planning something that we can have
> in the
> way SQLite is (not tied to any kind of restrictive license), we can share
> knowledge 
> and implement a solution like that. (PS: I don't have full time to work on
> it, but 
> I can help in free hours)
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Griggs, Donald
> Sent: segunda-feira, 12 de maio de 2008 10:47
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Distributed transaction best practices
> 
> Hi David,
> 
> 
> Regarding:  "What are the recommended "best practices" around using
> SQLite in a distributed scenario?"  [two-phase commit, etc.]
> 
> I trust that someone with some actual relevant knowledge will reply to
> your query later, but I imagine that many would say the the "recommend
> best practice" is *not* to use sqlite, since sqlite was designed to be
> an elegant embedded database -- without even one server -- let alone
> multiple synchronized ones.
> 
> I take it you have strong reasons for rejecting, say, Postgres, which
> now implements two-phase commmit right out of the box?  
>  
> http://www.postgresql.org/docs/current/static/sql-prepare-transaction.ht
> ml
> 
> You may already know everything in articles such as this one
>  
> http://en.wikipedia.org/wiki/Two_phase_commit#Distributed_two-phase_comm
> it_protocol
> And its references (I don't claim to), but I'm listing it here just it
> case it's helpful to you.
> 
> On the other hand, if you *do* develop a solid "distributed sqlite"
> implementation, I'm sure others would be interested.
> 
> Regards,
>   Donald Griggs
> 
>  
> 
> 
> This email and any attachments have been scanned for known viruses using
> multiple scanners. We believe that this email and any attachments are virus
> free, however the recipient must take full responsibility for virus
> checking. 
> This email message is intended for the named recipient only. It may be
> privileged and/or confidential. If you are not the named recipient of this
> email please notify us immediately and do not copy it or use it for any
> purpose, nor disclose its contents to any other person.
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> 
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Cannot get amalgamation built from CVS to compile

[Matthew L. Creech]

On Tue, May 13, 2008 at 12:28 AM, Samuel Neff <[EMAIL PROTECTED]> wrote:
>
>  One other issue we're having and are not sure about is we get a compiler
>  error on sqlite3_profile and sqlite3_trace.  We need to remove these two
>  lines from the def file included with the sqlite source in order to get
>  everything to compile ok on VS 2008.  are sqlite3_profile and sqlite3_trace
>  included by default in both the source and def or is there a mismatch?  Or
>  is there something else we should be doing besides editing the def file
>  manually?
>

Presumably you're either defining SQLITE_OMIT_TRACE or
SQLITE_OMIT_FLOATING_POINT, which omits both of those functions from
the build, and since sqlite3.def is static it has to be updated.  I'd
hazard a guess that updating it yourself is currently required, but I
don't build on Windows, so I'm really not sure - DRH would know more
about this.

The makefile does have a target to re-generate sqlite3.def on the fly,
but that's meant for Cygwin-based builds.

-- 
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Precompiled AIX Version?

[Derek Lee-Wo]

Is there a precompiled version of sqlite3 available for AIX?  I did a
Google search, but can't find anything.

I would build it myself, but I'm having a really hard time as the
configure script wouldn't run fully.  First it complains about grep,
even when I installed the GNU grep, but I hacked configure to get
around that and then it complained about not finding a suitable
linker.  I did set CC to be both gcc and cc.

At this point I would be happy to find a precompiled static sqlite3 library
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Mailing list

[Samuel Neff]

On Tue, May 13, 2008 at 3:13 PM, <[EMAIL PROTECTED]> wrote:

>
> I think mailing lists worked fine 20 years ago but does it have any
> advantage today ? :)
> Rado
>
>
That's just an opinion.. personally I prefer mailing lists because I can see
all seven lists I subscribe to in one place and check them daily.  On the
other hand the 4 bulletin boards that I try to follow I often forget about
and don't get to more than once a week because I have to go to each one
individually and each has it's own mechanisms for tracking new messages and
such.

Luckily as Igor mentioned there are several options for viewing this and
many other mailing lists through an online or nntp interface so that can
give the subscriber the choice.  Choice is good.

Sam

-- 
-
We're Hiring! Seeking passionate Flex, C#, or C++ (RTSP, H264) developer.
Position is in the Washington D.C. metro area. Contact
[EMAIL PROTECTED]
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] nVARCHAR as unique index

[Igor Tandetnik]

"Farzana" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> We are using SQLite and we have the table structure as CREATE TABLE
> Brand(PcNo numeric(4) Not Null,SubPcNo numeric(4) Not Null,BrandNo
> numeric(9) Not Null,BrandDescription nVARCHAR(254)Not Null,ST
> numeric(1),TS numeric(14)) where the index is CREATE UNIQUE index
> BrandKey1 on Brand(PcNo,SubPcNo,BrandNo). When we use this table in
> the application we are suppose to sort the datas by
> BrandDescription.So we tried to create a unique index as CREATE
> UNIQUE INDEX BrandKey2 on Brand(BrandDescription).But we couldn't
> able to create the unique index.

Define "couldn't able". What exactly seems to be the problem? Did you 
get an error message? What did the message say?

Is it possible that the values in BrandDescription column are not in 
fact unique? If they are not, then naturally you would get an error 
trying to create a unique index. Try this statement:

select * from Brand
group by BrandDescription
having count(*) > 1;

If this returns any rows, you have duplicates.

Igor Tandetnik 



___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Is this Sorting order right?

[Igor Tandetnik]

"Mahalakshmi.m"
<[EMAIL PROTECTED]> wrote
in message
news:[EMAIL PROTECTED]
> Igor Tandetnik wrote
>>> I can't reproduce this particular problem. Here's the test I wrote:
>>> Figure out what you are doing differently.
>
> I too did the same using both UTF8 anf UTF16 .Its coming right for
> UTF8 but its wrong for UTF16.

I'm not sure I understand. What exactly are you doing differently in 
these two cases? Can you quote the exact code that fails, in full?

Igor Tandetnik 



___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Better Update SQL

[Adler, Eliedaat]

Hi,
 
Exercise in SQL for all
 
Is there a better way to phrase this INSERT trigger text:
 
 
UPDATE ITEM
SET 

ITEM_SGT=   ifnull(ITEM_SGT,(SELECT SGT FROM SETUP))  ,
ITEM_EGT =  ifnull(ITEM_EGT,(SELECT EGT FROM SETUP)),
ITEM_SGT_MODE =  ifnull(ITEM__AUTO_SGT_MODE,(SELECT SGT_MODE
FROM SETUP)),
ITEM_EGT_MODE =  ifnull(ITEM_AUTO_EGT_MODE,(SELECT EGT_MODE FROM
SETUP))

WHERE ITEM__ID = NEW.ITEM__ID;
 
 
explanation: SETUP is a configurable table of defaults with a single row
of values
- when a row in inserted to ITEM - we want the trigger to populate the
default values if they have not been set by INSERT.
 
Eliedaat 
 
*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the [EMAIL PROTECTED] and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00

To protect the environment please do not print this e-mail unless necessary.
**

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Mailing list

[Igor Tandetnik]

<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I apologize if this is off topic but wouldn't it be better to use
> some standard discussion board, like PHPBB  instead of mailing list?

Subscribe through GMane (http://gmane.org/) and use a NNTP client. 
That's what I do.

Igor Tandetnik 



___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Mailing list

[rrrado2]

I apologize if this is off topic but wouldn't it be better to use some standard 
discussion board, like PHPBB  instead of mailing list? It is pain to use 
mailing lists (you have couple of them for sqlite), ((un)registration, posting, 
receiving tons of e-mails, searching, etc.).
Message from my other free email was rejected because of it's IP was listed at 
some spam list. I think mailing lists worked fine 20 years ago but does it have 
any advantage today ? :)
Rado
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] nVARCHAR as unique index

[Farzana]

Dear All,

We are using SQLite and we have the table structure as CREATE TABLE
Brand(PcNo numeric(4) Not Null,SubPcNo numeric(4) Not Null,BrandNo
numeric(9) Not Null,BrandDescription nVARCHAR(254)Not Null,ST numeric(1),TS
numeric(14)) where the index is CREATE UNIQUE index BrandKey1 on
Brand(PcNo,SubPcNo,BrandNo). When we use this table in the application we
are suppose to sort the datas by BrandDescription.So we tried to create a
unique index as CREATE UNIQUE INDEX BrandKey2 on Brand(BrandDescription).But
we couldn't able to create the unique index.

Is there any restriction in having nVARCHAR as unique index?

Kindly help in this regard.

Regards,
Farzana.
-- 
View this message in context: 
http://www.nabble.com/nVARCHAR-as-unique-index-tp17206197p17206197.html
Sent from the SQLite mailing list archive at Nabble.com.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] ATTACH problem

[D. Richard Hipp]

On May 13, 2008, at 7:57 AM, [EMAIL PROTECTED] wrote:

>
> Im running ATTACH database on SQlite 3.5.8 on windows.  
> Im opening one database
> file and attaching the second one.
> On my computer it works, but it fails at other computer. The  
> database is opened in more
> than one thread (it is failing in worker thread).
> sqlite3_step() returns SQLITE_MISUSE , but _sqlite3_errmsg() returns  
> "database is locked".
> What can be the problem?

What does sqlite3_threadsafe() return?

D. Richard Hipp
[EMAIL PROTECTED]



___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users