[sqlite] LINQ to SQLite Cannot Update: "Store update, insert, or delete statement affected an unexpected number of rows"

2015-05-31 Thread Etienne Charland
I did some more tests. The way it handles GUID between text and binary is screwed up. When updating data, it will update as binary even if BinaryGUID is false. When selecting data, however, it tries to select it as plain text so nothing matches the query. Etienne From: mystery...@hotmail.com

[sqlite] LINQ to SQLite Cannot Update: "Store update, insert, or delete statement affected an unexpected number of rows"

2015-05-31 Thread Etienne Charland
Oh. I see what you were trying to say. The error I was having was not because GUID isn't supported, but because it was trying to interpret the data as binary while it was stored as text, thus the request failed. I just tried creating a new table with a primary key of type 'uniqueidentifier', an

[sqlite] LINQ to SQLite Cannot Update: "Store update, insert, or delete statement affected an unexpected number of rows"

2015-05-31 Thread Joe Mistachkin
Etienne Charland wrote: > > I just tried creating a new table with a primary key of type > 'uniqueidentifier', and adding data into it. It shows up as > binary data. > This is also controlled by the "BinaryGUID" (no spaces) connection string property. Here is an example connection string:

[sqlite] LINQ to SQLite Cannot Update: "Store update, insert, or delete statement affected an unexpected number of rows"

2015-05-31 Thread Etienne Charland
The point I'm trying to make is not about whether GUID gets stored as binary or text... but rather that currently it's not working at all. There's no reason why GUIDs shouldn't be supported and should crash when trying to do an update. Etienne > From: sqlite at mistachkin.com > To: sqlite-use

[sqlite] LINQ to SQLite Cannot Update: "Store update, insert, or delete statement affected an unexpected number of rows"

2015-05-31 Thread Joe Mistachkin
Etienne Charland wrote: > > The point I'm trying to make is not about whether GUID gets stored as > binary or text... > First, the exception being thrown here originates from deep within the .NET Framework itself and indicates that the number of rows impacted by the query did not match expectatio

[sqlite] Possible Bug

2015-05-31 Thread Simon Slavin
On 31 May 2015, at 2:22am, Alan Bryan wrote: > SELECT *, Sum(MyField) AS MySumField FROM MyTable > > Now run sqlite3 and type the following: > > PRAGMA table_info(MyView); > > You will notice there is no data type for some reason. I think you get datatypes only for exact copies of a source

[sqlite] LINQ to SQLite Cannot Update: "Store update, insert, or delete statement affected an unexpected number of rows"

2015-05-31 Thread Etienne Charland
SQLite doesn't have support for many data types, but in fact it just doesn't have many restrictions. It doesn't have data types but affinities. When defining a column as "uniqueidentifier" in SQLite, it still stores the data as text. It would be the .NET provider's job to convert it back and for

[sqlite] Sqlite download page links AWOL

2015-05-31 Thread Teg
Hello Stephen, Yeah it's back to normal for me too. Basically the whole top section was missing. C Saturday, May 30, 2015, 8:55:18 PM, you wrote: SC> Something JUST changed within the last 60 seconds. I saw what the OP said, SC> but, it reverted back to the list of download links. Weird. S

[sqlite] LINQ to SQLite Cannot Update: "Store update, insert, or delete statement affected an unexpected number of rows"

2015-05-31 Thread Joe Mistachkin
Etienne Charland wrote: > > When defining a column as "uniqueidentifier" in SQLite, it still stores the > data as text. It would be the .NET provider's job to convert it back and > forth to Guid. > This depends on the value of the BinaryGUID connection string property. You might want to experim

[sqlite] Possible Bug

2015-05-31 Thread Keith Medcalf
The "data type" is associated with the data value itself. Columns do not have Datatypes -- they have affinities. The column affinity is only used when doing certain and specific operations on real tables. Since you cannot do these operations on a view, the column affinity is meaningless and

[sqlite] INSERT OR REPLACE and INSERT/DELETE/UPDATE triggers

2015-05-31 Thread David Barrett
Ah, naturally I found the answer right after sending this. The secret: PRAGMA recursive_triggers = 1; As stated here: https://www.sqlite.org/lang_conflict.html "When the REPLACE conflict resolution strategy deletes rows in order to satisfy a constraint, delete triggers fire if and only if recur