I note that SQLite prevents creation of indexes with the same
name, regardless of table.
Quite. So it's unclear why you would want to be able to mention
table name in the DROP INDEX statement.
Fair enough! It does seem strange when an index is associated with a
single table to delete it
Matthew Allen [EMAIL PROTECTED] writes:
There may be another variable that I didn't mention in my first post, and that
is I'm compiling sqlite using
Visual C++ 6 on windows atm and maybe there is a problem that only shows up in
VC6 and not in gcc. So with that in
mind I'm building the Mac port
Hi Roger,
I got your mail id from one of my friend - I am facing some issues while
working with Sqlite 3.6.4, could you please clarify those things.
Actually I am upgrading Sqlite for one product from Sqlite 3.2.5 to Sqlite
3.6.4 version.
I have dowloaded *sqlite-amalgamation-3_6_4 *from sqlite
Hi,
pardon me if this is a pretty easy SQL question, yet i am after a
statement compound which applies just ONE where clause to a group of
tables.
Something like
select * from c1,c2,c3where foo110
with foo1 being in all of the specified tables. So far, all i can see is
that I have
Christophe Leske [EMAIL PROTECTED]
wrote in message news:[EMAIL PROTECTED]
pardon me if this is a pretty easy SQL question, yet i am after a
statement compound which applies just ONE where clause to a group of
tables.
Something like
select * from c1,c2,c3where foo110
Perhaps
Hello.
First I want to apologise because my english is very poor.
I have an aplication that contains an SQLite 2.1 database. This application
was made in visual basic 6 and i use the ags_sqlite dll to manage the
database. Now i need to encrypt the data base.
The problem is that i have different
Christophe Leske [EMAIL PROTECTED] writes:
Hi,
pardon me if this is a pretty easy SQL question, yet i am after a
statement compound which applies just ONE where clause to a group of
tables.
Something like
select * from c1,c2,c3where foo110
with foo1 being in all of the
On Nov 18, 2008, at 5:10 AM, Roshan Sullad wrote:
[...]
I have another Visual studio test application where I am using this
Sqlite3.dll functionality, I have linked statically to Sqlite3.dll by
including *sqlite3.c,sqlite3.h,sqlite3ext.h* , files in to my test
application project. And am
I am treading on uncharted waters (for me), but my understanding is that...
On Tue, 18 Nov 2008 08:07 + (GMT Standard Time), Hugh Gibson
[EMAIL PROTECTED] wrote:
I note that SQLite prevents creation of indexes with the same
name, regardless of table.
Quite. So it's unclear why
On 11/18/08, Christophe Leske [EMAIL PROTECTED] wrote:
Hi,
pardon me if this is a pretty easy SQL question, yet i am after a
statement compound which applies just ONE where clause to a group of
tables.
Something like
select * from c1,c2,c3where foo110
with foo1 being in
When you add multiple tables into the FROM clause, you make a single
conceptual table out of them by using the JOIN operator.
So
(with c1,c2,c3 all being rtrees)
select * from (select * from c1,c2,c3) where bla10
is *not the same as
select * from c1 where bla10
union all
select * from c2
Perhaps something like this:
select * from
(select * from c1
union all
select * from c2
union all
select * from c3
...
)
where foo1 10;
Yes!
And to answer MikeĀ“s email as well:
these table represent higher and detailled data for deeper research, so all of
these tables have
I'm working with an application that keeps a list of clients:
CREATE TABLE clients (
id integer primary key,
fingerprint varchar (40) unique,
...
);
Clients are uniquely identified by fingerprint but are referenced
by an integer id in most places in the database.
Clients can be
Hi all,
I create a table with 200 columns, then use sqlite3_prepare() and
sqlite3_step()
to get a record by this: select * from tbl where ID =.. . Test in my
embedded system
The total time is about 65ms,it is too long for the performance
requirement, I found
On 11/18/08, Christophe Leske [EMAIL PROTECTED] wrote:
When you add multiple tables into the FROM clause, you make a single
conceptual table out of them by using the JOIN operator.
So
(with c1,c2,c3 all being rtrees)
select * from (select * from c1,c2,c3) where bla10
is *not the
[EMAIL PROTECTED] writes:
Can't make the 'name' column
'unique' as two clients may have the same name. Can't make
the 'id' column 'unique' as a client may have more than one
name...
However you can specify that the name/id pair is unique ...
PRIMARY KEY (name, id)
Regards,
MikeW
On 20081118 15:25:32, MikeW wrote:
[EMAIL PROTECTED] writes:
Can't make the 'name' column
'unique' as two clients may have the same name. Can't make
the 'id' column 'unique' as a client may have more than one
name...
However you can specify that the name/id pair is unique
Hi,
We have recently upgraded from 3.5.9 to 3.6.5 and one of tests that ensures
certain SQLite behavior now fails. The test basically checks how cache spill is
handled:
SESSION THREAD 1SESSION THREAD 2
Open session
Launch SELECT, keep stmt
(assert SHARED lock is held)
On Nov 19, 2008, at 12:27 AM, Igor Sereda wrote:
Hi,
We have recently upgraded from 3.5.9 to 3.6.5 and one of tests that
ensures certain SQLite behavior now fails. The test basically checks
how cache spill is handled:
SESSION THREAD 1SESSION THREAD 2
Open session
Regarding: Problem: Exception message: The database disk image is
malformed.
Ernany, I wasn't sure if you were commenting further on Joanne Pham's
database or were you writing because you have a similar problem with a
different database.
In either case, you both may want to refer to the very,
Hi ,
I tried to execute the test cases (all test) but after around 2 hours at
sqlimit testcase execution i got this result
sqllimits1-16.2...unable to alloc 171798693 bytes
my question is that how much memory does it need for full execution of the
test cases before starting the execution.
Clients can be referred to by one or more names and so there's
another table:
CREATE TABLE client_names (
id integer,
name text
);
Names aren't unique. Two clients can have the same name.
But the combination of id and name are unique: hence try this:
CREATE TABLE
An index is actually indeed associated with a table, and within that
table with one or more columns.
Hence, dropping an index doesn't require a table name.
I can easily write SQL like this:
CREATE TABLE First (nID, nValue)
CREATE INDEX idxID ON First (nID)
CREATE TABLE Second (nID, nValue,
Hi!
I am basically a windows application developer. I am developing an
application for desktop which uses a database. I choose SQLite as my
database and my issue is if any one finds my application is using SQLite
database they can corrupt my database or they can see the contents of my
24 matches
Mail list logo