System.Data.SQLite: View Ticket

2015-07-14
19:30		• Closed ticket [964063da16]: SQLiteConnection.Flags property not properly observed plus 4 other changes artifact: 7d8fffc3dd user: mistachkin
19:29		Honor the pre-existing flags for connections during the Open method. Fix for [964063da16]. check-in: f7cac79346 user: mistachkin tags: trunk
17:59		• Ticket [964063da16] SQLiteConnection.Flags property not properly observed status still Open with 5 other changes artifact: fe28f5ced8 user: mistachkin
17:47		• Ticket [964063da16]: 5 changes artifact: b5323636b3 user: mistachkin
11:55		• New ticket [964063da16]. artifact: 3399e34b8c user: anonymous

Ticket Hash:	964063da1641cc87ad9c95fce2114173d078d33b
Title:	SQLiteConnection.Flags property not properly observed
Status:	Closed	Type:	Code_Defect
Severity:	Important	Priority:	Blocker
Subsystem:	Connection	Resolution:	Fixed
Last Modified:	2015-07-14 19:30:37
Version Found In:	latest (2015-07-13 22:41:47)
User Comments:
anonymous added on 2015-07-14 11:55:08: I think that the SQLiteConnection.Flags property is not properly appreciated: when it is set out of the connection string but before opening the connection and not setting the DefaultFlags property, then the private FallbackDefaultFlags are used. `using (var connection = new SQLiteConnection("Data Source=myDatabase.db3")) { if (!((connection.Flags \| SQLiteConnectionFlags.GetAllAsText) == SQLiteConnectionFlags.GetAllAsText)) connection.Flags \|= SQLiteConnectionFlags.GetAllAsText; connection.Open(); // manually set flag is lost here ... }` mistachkin added on 2015-07-14 17:59:37: Issue confirmed. Fix will be available shortly. mistachkin added on 2015-07-14 19:30:37: Fixed on trunk via check-in [f7cac79346].