Re: [sqlite] PRAGMA foreign_keys = ?, feature request

Joe Mistachkin wrote: [regarding foreign key enforcement when user does not directly open connections] > If anybody knows how to solve this more easily than suggested above, I > would appreciate your input. > There are two ways to solve this: 1. The 1.0.83.0 release of System.Data.SQLite, due

Re: [sqlite] PRAGMA foreign_keys = ?, feature request

Larry Brasfield wrote: ... The framework opens and closes the database, presumably like it treats other DB connections. The schema that it sets up for objects related to each other relies on foreign keys. Unfortunately, foreign key enforcement in SQLite, as now specified and implemented, only

Re: [sqlite] PRAGMA foreign_keys = ?, feature request

Larry Brasfield wrote: > > If anybody knows how to solve this more easily than suggested above, I > would appreciate your input. > There are two ways to solve this: 1. The 1.0.83.0 release of System.Data.SQLite, due out before the end of the year, adds a static Changed event to the

Re: [sqlite] PRAGMA foreign_keys = ?, feature request

Hi Larry, I think I had similar problem once.  Here was the solution I found for it: http://www.mail-archive.com/sqlite-users@sqlite.org/msg73131.html HTH, David Richardson From: Larry Brasfield To: SQLite Users mailing list

[sqlite] PRAGMA foreign_keys = ?, feature request

I have a situation here that I expect will apply to others as Microsoft's "Entity Framework" is used with System.Data.SQLite . The framework opens and closes the database, presumably like it treats other DB connections. The schema that it sets up for objects related to each other relies on

Re: [sqlite] strange behavior with integer with where clause

Patrik Nilsson wrote: > When I perform a select as the following > > select * from repetition where interval>0 and id=617 > > the result is unexpected > > 617|2012-12-23 19:30:46|0|2012-12-23 19:30:46|0|1|1|0 My educated guess is, interval column has a string value

Re: [sqlite] Trigger blocks a single transaction?

Okay, sorry, I didn't understand your initial email correctly. So the answer to your question is yes, trigger is executed as a single transaction and if first statement fails then other do not execute. The only exception is when you have ON CONFLICT IGNORE. Do you observe a different behavior? Can

Re: [sqlite] Trigger blocks a single transaction?

On Monday 24 December 2012 11:04:29 Alem Biscan wrote: > Hi, > > No, i do not execute begin/commit. It is VIEW'S INSTEAD OF UPDATE TRIGGER. > I am doing a regular update to the view from C#. Another thing is that view > doesn't return any row affected value. Well it makes sense somehow.. It >

Re: [sqlite] Trigger blocks a single transaction?

Hi, No, i do not execute begin/commit. It is VIEW'S INSTEAD OF UPDATE TRIGGER. I am doing a regular update to the view from C#. Another thing is that view doesn't return any row affected value. Well it makes sense somehow.. It cannot know how many view's visible rows were affected. It lowers the

Re: [sqlite] Trigger blocks a single transaction?

Do you execute all updates as one call to sqlite_exec? Or as separate calls to sqlite_exec or sqlite_prepare/sqlite_step? If separate then do you check return value from the calls? And do you execute BEGIN/COMMIT somewhere? Pavel On Sun, Dec 23, 2012 at 2:37 PM, Alem Biscan

[sqlite] Trigger blocks a single transaction?

Hello, I am wandering if i have a block of dml statements in a trigger ( instead of ). Is it a single transaction? If something fails everything fails or? SELECT CASE WHEN NOT EXISTS ( SELECT klas_sifra FROM klasifikacija kl , tipklas tk WHERE kl . tkla_id = tk . tkla_id AND kl . klas_sifra =

Re: [sqlite] strange behavior with integer with where clause

Since I have blobs, datetimes, and integers I managed to use the hex-convertion on some integers as well. They are stored as text in my program. I changed the code for the interval integer, so it is inserted as an integer. It seems to work. I don't get this strange kind of selection anymore.

Re: [sqlite] strange behavior with integer with where clause

Patrik Nilsson wrote: After dumping the database I found that the line of insertion looks like this INSERT INTO "repetition" VALUES(617,X'323031322D31322D32332031393A33303A3436',X'30',X'323031322D31322D32332031393A33303A3436',0,1,1,0); Does SQLite manage the insertion with hexadecimal

Re: [sqlite] strange behavior with integer with where clause

On 23 Dec 2012, at 8:42pm, Patrik Nilsson wrote: > After dumping the database I found that the line of insertion looks like > this > > INSERT INTO "repetition" >

Re: [sqlite] strange behavior with integer with where clause

On Sun, Dec 23, 2012 at 2:51 PM, Patrik Nilsson wrote: > Hi All! > > When I perform a select as the following > > select * from repetition where interval>0 and id=617 > > the result is unexpected > > 617|2012-12-23 19:30:46|0|2012-12-23 19:30:46|0|1|1|0 > What does

Re: [sqlite] strange behavior with integer with where clause

Patrik Nilsson wrote: > What do you get with query > select * from repetition where cast(interval as integer)==0 and > interval>0 "select * from repetition where cast(interval as integer)==0 and interval>0 and id=617" With this I get the same as the strange one. Without "id=617" it is still

Re: [sqlite] strange behavior with integer with where clause

> What do you get with query > select * from repetition where cast(interval as integer)==0 and > interval>0 "select * from repetition where cast(interval as integer)==0 and interval>0 and id=617" With this I get the same as the strange one. Without "id=617" it is still selected. /Patrik On

Re: [sqlite] strange behavior with integer with where clause

Patrik Nilsson wrote: When I perform a select as the following select * from repetition where interval>0 and id=617 the result is unexpected 617|2012-12-23 19:30:46|0|2012-12-23 19:30:46|0|1|1|0 It shows a result with "interval" zero, although I requested everything above zero. When I

Re: [sqlite] parameters in a view, disallowed? (docs issue)

Kevin Benson wrote: At least, there's this: http://sqlite.org/docsrc/info/7276f4a4a3e338ea187cb5e50c57e4f9806aed89?sbs=0 +ERROR_MSG {parameters are not allowed in views} { + The right-hand side of a CREATE VIEW (that is to say, + the SELECT statement that defines the view) may not contain +

[sqlite] strange behavior with integer with where clause

Hi All! When I perform a select as the following select * from repetition where interval>0 and id=617 the result is unexpected 617|2012-12-23 19:30:46|0|2012-12-23 19:30:46|0|1|1|0 It shows a result with "interval" zero, although I requested everything above zero. When I select using the

Re: [sqlite] sqlite3.c:134542: warning: assignment from incompatible pointer type

Pavel Volkov wrote: Please consider the following error: sqlite3.c: In function 'deserializeGeometry': sqlite3.c:134542: warning: assignment from incompatible pointer type And the patch for it. Three questions arise from your message: 1. Which version of sqlite3.c ? (It's not the latest,

Re: [sqlite] sqlite3.c:134542: warning: assignment from incompatible pointer type

On 23 Dec 2012, at 11:51am, Pavel Volkov wrote: > sqlite3.c: In function 'deserializeGeometry': > sqlite3.c:134542: warning: assignment from incompatible pointer type The authors don't normally worry about warnings, since it is impossible to get rid of all warnings

[sqlite] sqlite3.c:134542: warning: assignment from incompatible pointer type

Hello. Please consider the following error: sqlite3.c: In function 'deserializeGeometry': sqlite3.c:134542: warning: assignment from incompatible pointer type And the patch for it. ___ sqlite-users mailing list sqlite-users@sqlite.org