Paul Bainter wrote:
>
> When deploying my application to a clean Windows 7 x64 virtual machine
> (VMWare Workstation 10), I got the message "Failed to find or load the
> registered .NET Framework Data Provider" and of course with no database
> the app would crash.
>
When does this error appea
On 20 Oct 2013, at 6:11pm, Bogdan Ureche wrote:
> Sorry, I misread your reply
In your defence, my writing was ambiguous.
> You are correct. In your scenario, after step
> 3 the trigger references a table that no longer exists.
As an alternative one could ALTER TABLE RENAME the table to someth
Sorry, I misread your reply. You are correct. In your scenario, after step
3 the trigger references a table that no longer exists. A similar issue
exists with foreign keys.
Bogdan
On Sun, Oct 20, 2013 at 10:11 AM, Simon Slavin wrote:
>
> On 20 Oct 2013, at 4:09pm, Bogdan Ureche wrote:
>
> >
On 20 Oct 2013, at 4:09pm, Bogdan Ureche wrote:
> I tried without success to reproduce this scenario.
>
> create table t1(c);
> create temporary trigger tr1 after insert on t1 begin select raise(abort,
> 'error'); end;
> insert into t1(c) values(1); -- error is raised here
> drop table t1;
> cr
> The problem is not that table names aren't qualified. The problem is that
> information for setting up the schema (structural components) of a SQLite
> database are stored in the database as the SQL commands rather than a
> complicated internal format. This makes it permissable to do this:
>
>
On 20 Oct 2013, at 12:23pm, Raheel Gupta wrote:
>> Yes, but they allow the searches to be faster. You are making it longer
>> to do INSERT but shorter to do SELECT. Which is best for you depends on
>> your purposes.
>
> I need the inserts to be faster.
> So which is better ? An Index or a Pri
On 20 Oct 2013, at 3:34am, Bogdan Ureche wrote:
> Thank you for replying and for updating the documentation. I didn't realize
> that the trigger may be unexpectedly reattached to a different table when
> the schema changes. If this is the case then perhaps the creation of temp
> triggers on non-
Raheel Gupta wrote:
>> Yes, but they allow the searches to be faster. You are making it longer
>> to do INSERT but shorter to do SELECT. Which is best for you depends on
>> your purposes.
>>
>
> I need the inserts to be faster.
> So which is better ? An Index or a Primary Key ?
Is there any dif
>
> Yes, but they allow the searches to be faster. You are making it longer
> to do INSERT but shorter to do SELECT. Which is best for you depends on
> your purposes.
>
I need the inserts to be faster.
So which is better ? An Index or a Primary Key ?
The new INDEX that I created on your suggest
9 matches
Mail list logo