Thanks! I'll give that a try.
Jeff
Richard Klein wrote:
>> Whether or not the the secondary columns are needed is a function of one
>> of the primary columns. That function involves values from another
>> table, though, so the general case would require a join. That other
>> table is
> Whether or not the the secondary columns are needed is a function of one
> of the primary columns. That function involves values from another
> table, though, so the general case would require a join. That other
> table is small, however, so I generally cache it outside the database.
>
Whether or not the the secondary columns are needed is a function of one
of the primary columns. That function involves values from another
table, though, so the general case would require a join. That other
table is small, however, so I generally cache it outside the database.
Some
> I'm pretty new to databases, and I have a schema design question. I
> don't know enough about the guts of how sqlite works to know how to make
> some tradeoffs. I have a large (potentially millions of entries) table
> and it has 4 columns which are needed for every entry, and 4 more that
I'm pretty new to databases, and I have a schema design question. I
don't know enough about the guts of how sqlite works to know how to make
some tradeoffs. I have a large (potentially millions of entries) table
and it has 4 columns which are needed for every entry, and 4 more that
are
All,
Are there database schema's (eg. for Phonebook ) available on the net?
Thanks
Shilpa
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
Hello, I'm SQLiteDBMS developer.
SQLiteDBMS is minor F/OSS project for SQLite3 via TCP/IP network.
http://sqlitedbms.sf.net
SQLiteDBMS will support replication on next release. Normal SQL and
prepared statement was captured by sqltie3_*_hook.
But, "CREATE ...", "DROP ..." and "ALTER ..."
The only way for a database connection to know if the schema
has changed is to open and read the database file. Sqlite_prepare()
tries to avoid reading the database file in order to reduce
contention, though, so it is unlikely to discover a database
change. The change is only discovered when
Matthew Jones <[EMAIL PROTECTED]> wrote:
> what should our program do prior to
> preparing a statement to ensure that its view of the database schema is
> correct?
>
The only way for a database connection to know if the schema
has changed is to open and read the database file.
We have a problem that is obviously to do with our failing to understand
sqlite properly. Using a test program (enclosed) we create a table in a
new database and then wait (for use input). If we then open the same
sqlite database using sqlite3 and create another table in the database
when we
I apologise in advance as this topic has been done to death.
Can I assume that a schema error can only occur when calling
sqlite3_step?
I've trawled through the documentation but cant find a definitive
answer.
Thanks,
Daniel.
--
Daniel Shields
Equities IT
+44(0)207 888 9248
[EMAIL
>I have SQLite schema in an ascii file. I would like to be able to load
>this schema via SQLite C-API. How do I do this?
You can look at the source code for the SQLite shell
and see how it implements the .read command, but it
may be simpler just to invoke the SQLite shell using
system() o
In a previous thread about sqlite_schema, I commented that there *is* a case
where
SQLITE_SCHEMA does get raised as an error, although DRH said that this is
not possible in
version 3.x. It turns out that I was wrong. The scenario I described does
raise an error,
but it is not SQLITE_SCHEMA, it is
Wow - that was fast!
Any plans for a 3.0.8?
Eddy
On Tue, 2004-10-05 at 16:44, D. Richard Hipp wrote:
> Eddy Macnaghten wrote:
> > This does not seem to work for 3.0.7
> >
> >
> >>Marc Pitoniak wrote:
> >>
> >>>To get the schema of a table T from A I've tried "PRAGMA table_info('A.T') "
>
Eddy Macnaghten wrote:
This does not seem to work for 3.0.7
Marc Pitoniak wrote:
To get the schema of a table T from A I've tried "PRAGMA table_info('A.T') "
among other things without any success.
PRAGMA A.table_info(T);
Fixed with check-in [2001]
This does not seem to work for 3.0.7
If you have a table named "t" in the main database, and you attach a
database that has a table named t in it as attachdb, then
pragma attachdb.table_info(t);
still seems to give the info for the table t in the main database.
Is this a bug or have I got it
Thank you very much.
-Marc
-Original Message-
From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 05, 2004 8:09 AM
To: [EMAIL PROTECTED]
Subject: Re: [sqlite] Schema of an attached database
Marc Pitoniak wrote:
>
> To get the schema of a table T from A I've
Marc Pitoniak wrote:
To get the schema of a table T from A I've tried "PRAGMA table_info('A.T') "
among other things without any success.
PRAGMA A.table_info(T);
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
101 - 118 of 118 matches
Mail list logo
