On 3/5/2015 9:56 PM, Scott Robison wrote:
> Finally, my question: Is there some sort of syntax that I'm missing that
> would "simplify" my schema with a single update trigger, or is this the
> proper way to "update" individual columns of a view?
Imagine that the "clean" table has null in column X
On 5 Mar 2015, at 9:23pm, RNACS - Info wrote:
> Does not help. I put a breakpoint at the "SQLconn = Nothing" statement &
> checked the value of SQLconn.State. It was "Closed", so I continued one &
> still got the error.
Okay. Worth checking. I'm afraid I don't know your API well enough to su
> On 5 Mar 2015, at 8:34pm, RNACS - Info wrote:
>
> The code I am using is:
>
>' Close license database connection
>If Not IsNothing(SQLconn) Then
>If SQLconn.State <> ConnectionState.Closed Then
>SQLconn.Close()
>End If
>SQLc
I have a use case to update a view, and wanted to make sure I'm not missing
anything obvious.
The basics of my schema are that I have a table from a third party that
might be updated at any time. A lot of the data in that table is garbage
though, and I want cleaner data, so I have a parallel table
Hmm, yes this will work. Though re-educating users writing their own queries
to avoid like in this case will be an ongoing challenge. :) But I do
understand that generic 'like' support for Virtual Tables given the ability to
override would be very challenging to implement generically.
MikeN
> I'm using System.Data.SQLite version 1.0.95.0 and have what appears to
> be a bug with Virtual Tables. Queries using 'like' in the where
> clause are not getting the like clause passed to BestIndex as a query
> constraint.
> Specifically:
>
>
> - Simple query: select * from foo where
1.0.96.0 is already released and its bug fix only per the release notes:
System.Data.SQLite version 1.0.96.0 (with SQLite 3.8.8.3) is now available on
the System.Data.SQLite website:
https://system.data.sqlite.org/
Further information about this release can be seen at
https://system.
I'm using System.Data.SQLite version 1.0.95.0 and have what appears to be a bug
with Virtual Tables. Queries using 'like' in the where clause are not getting
the like clause passed to BestIndex as a query constraint. Specifically:
- Simple query: select * from foo where name like 'a%
On 2015-03-05 04:29 PM, Oskar Schneider wrote:
> Yes i already wonder why this table creating looks so much different from the
> other table, because i needed many loops.This is the new
> version:db.execute("""CREATE TABLE IF NOT EXISTS TRAVELDAYS
> (TaskUID INTEGER PRIMARY KEY AUTOINCRE
Simon,
Does not help. I put a breakpoint at the "SQLconn = Nothing" statement &
checked the value of SQLconn.State. It was "Closed", so I continued one &
still got the error.
Ray
-Original Message-
From: sqlite-users-boun...@mailinglists.sqlite.org
[mailto:sqlite-users-bounces at mailin
No. Any commands will have finished before the user can get to the screen
that allows them to move the data files.
Ray Andrews
-Original Message-
From: sqlite-users-boun...@mailinglists.sqlite.org
[mailto:sqlite-users-bounces at mailinglists.sqlite.org] On Behalf Of J Decker
Sent: Thursd
I have a program written in Visual Basic .NET.
One of the functions of the program is to move all of the program's data,
including a SQLite database to a different folder.
The program is a 32-bit application using System.Data.SQLite.dll.
I am having a problem that after I copy the data to the ne
On 2015-03-05 03:00 PM, Oskar Schneider wrote:
> I just created for each day a seperate column is this worse than your
> approach?
>
>
> Hick Gunter schrieb am 8:01 Donnerstag, 5.M?rz
> 2015:
>
>
>
That's around 1000 columns, right? Beware that SQLite has a standard
upper l
Yes i already wonder why this table creating looks so much different from the
other table, because i needed many loops.This is the new
version:db.execute("""CREATE TABLE IF NOT EXISTS TRAVELDAYS
(TaskUID INTEGER PRIMARY KEY AUTOINCREMENT,
Day INT NOT NULL,
On 3/5/15, Mike Nicolino wrote:
> Incidentally, this used to 'work' in a much older version of SQLite, though
> the semantics may not have been correct in all cases. Version 3.7.7.1,
> ended up transforming like to of pair of constraints in the "like 'a%'" case
> which were passed to BestIndex.
>
With the query the OP described he is interested only in one day at a time so
this won't hurt.
I am anticipating a question regarding variable column names in a query though.
-Urspr?ngliche Nachricht-
Von: R.Smith [mailto:rsmith at rsweb.co.za]
Gesendet: Donnerstag, 05. M?rz 2015 14:33
A
I strongly suggest you read up on database theory. An array should be
implemented as a separate table (unless perhaps it contains only a small number
of repeats and fields, where it may be faster). This is clearly not the case.
I assume your ?day array? is located at the end of the table definit
On 3/5/15, Mike Nicolino wrote:
> I'm using System.Data.SQLite version 1.0.95.0 and have what appears to be a
> bug with Virtual Tables. Queries using 'like' in the where clause are not
> getting the like clause passed to BestIndex as a query constraint.
> Specifically:
>
>
> - Simple qu
I just created for each day a seperate column is this worse than your approach?
Hick Gunter schrieb am 8:01 Donnerstag, 5.M?rz 2015:
#yiv6530489154 P.yiv6530489154ImprintUniqueID {MARGIN:0cm 0cm
0pt;}#yiv6530489154 LI.yiv6530489154ImprintUniqueID {MARGIN:0cm 0cm
0pt;}#yiv6530489154 DIV
On Mar 5, 2015, at 12:30 PM, Mike Nicolino
wrote:
> I'm using System.Data.SQLite version 1.0.95.0 and have what appears to be a
> bug with Virtual Tables. Queries using 'like' in the where clause are not
> getting the like clause passed to BestIndex as a query constraint.
> Specifically:
>
do you have any ... SqliteCommand's laying around that aren't finished?
On Thu, Mar 5, 2015 at 12:34 PM, RNACS - Info wrote:
> I have a program written in Visual Basic .NET.
>
> One of the functions of the program is to move all of the program's data,
> including a SQLite database to a different
> On 5 Mar 2015, at 7:28am, Alexandr N?mec wrote:
>
> Hi Simon,
>
>> Does SQLite automatically detect and uncorrupt these problems the next time
>> it opens the database,
>> or has something been done to the hardware to break in-order writing ?
>
> No. The database can be opened successful
I have been reading there are a few issues with v 95, so I am waiting for
the next. Will there be a version that has only bug fixes or new features as
well? As many of you know, new features usually also create regressions.
Thanks
Andy
If you can .dump it, can you also use .read to restore it? And if so, how
damaged does it appear to be?
My databases, with a corrupt index, couldn't be restored directly, but
the duplicate entries could be seen, cleaned up, and then the restore
succeeded. Or (more conveniently) remove the index
Hi Dave,
?
thanks for yoyr?reply.
?
>I'd be interested if you could characterize the corruption.
?
As I already replied to Simon, I can ".dump" the database but I can't run any
''select" queries. The SQLite shell displays "database disk image is malformed"
and using C?API, error code 11?(SQLITE_C
Hi Simon,
?
> Does SQLite automatically detect and uncorrupt these problems the next time
> it opens the database,
>?or has something been done to the hardware to break in-order writing ?
?
No. The database can be opened successfully, but a simple "select" ends up with
"database disk image is mal
Since you give no indication of the schema you are using:
Create table task (id integer primary key, ?.);
Create table todo ( task_id integer, day_no integer, foreign key (task_id)
references task (id ) on delete cascade on update cascade );
Create unique index todo_day on todo (day_no, task_id)
27 matches
Mail list logo
