D 2020-05-18T09:27:05.217
J foundin 1.0.111.0
J icomment We\sare\susing\sSystem.Data.SQLite\sdll\swith\sversion\s1.0.111.0\sfor\sone\sof\sthe\sdatabase\soperation.\r\n\r\nIn\sthis\soperation,\swe\sare\screating\sa\snew\ssqlite\sconnection\swith\sfollowing\sproperties.\r\n\r\nvar\sconnectionStringBuilder\s=\snew\sSQLiteConnectionStringBuilder\r\n\s\s\s\s\s\s\s\s\s\s\s\s{\r\n\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\sSyncMode\s=\sSynchronizationModes.Normal,\r\n\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\sVersion\s=\s3,\r\n\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\sDataSource\s=\sfileInfo.FullName,\r\n\s\s\s\s\s\s\s\s\s\s\s\s\s\s\s\sReadOnly\s=\sfalse,\r\n\s\s\s\s\s\s\s\s\s\s\s\s};\r\n\r\nOnce\swe\screate\sa\snew\sinstance\sof\sconnection,\sopening\sthe\sconnection\sand\screating\sa\ssimple\stable\swith\sfollowing\squery\swithin\sa\stransaction.\r\n\r\nCREATE\sTABLE\sIF\sNOT\sEXISTS\sTestTable(\sGuid\sBlob,\sIncrement\sINTEGER\sNOT\sNULL\s)\r\n\r\nSuccessfully\sable\sto\screate\sthe\stable.\r\n\r\nIn\sour\snext\sbusiness\slogic,\swe\sneed\sto\squery\sthis\stable\sto\sread\ssome\sdata\sand\sthis\scall\sis\shappening\sin\sa\sanother\sthread\susing\sa\ssame\sconnection\swhich\sis\salready\screated\sduring\screation\sof\stable.\sThis\soperation\sis\sstill\sa\ssynchronous\soperation.\r\n\r\nSELECT\sIncrement\sFROM\sTestTable\sWHERE\sGuid\s=\s@Guid\r\n\r\nProblem\sStatement:\r\n\r\nWhenever\swhile\sexecuting\sthe\sabove\smentioned\sselect\sstatement\swe\sare\sgetting\sfollowing\serror\sin\sApplication\sConsole:\r\n\r\n"SQLite\serror\s<17>:\sStatement\saborts\sat\s9:\s[SELECT\sIncrement\sFROM\sTestTable\sWHERE\sGuid\s=\s@Guid]\sDatabase\sschema\shas\schanged"\r\n\r\nOur\sAnalysis\son\sthis\sissue:\r\n1.\sWhenever\sthis\serror\slogs\sin\sour\sconsole,\snot\sgetting\sSQLite\sException\sor\sany\sbase\sexception(verified\sthrough\sour\slogging\smechanism).\r\n2.\sThis\serror\snot\scausing\sany\sissues\sto\sour\sworkflows.\sHence\snot\sseeing\sany\sside\seffects\sor\sapplication\scrash.\r\n3.\sThis\serror\snot\soccurring\swhen\swe\sdo\sthe\sSELECT\soperation\ssecond\stime.\sHence\serror\sis\scoming\sduring\sfirst\sSELECT\soperation\sonly.\s\r\n4.\sWe\sare\sable\sto\ssee\sthe\ssame\serror\swith\searlier\sversion\sof\sSystem.Data.SQLite(1.0.102.0)\r\n\r\nWorkaround\swe\sfound\sto\savoid\sthis\serror\sin\sconsole:\r\n1.\sCreate\snew\sSQLite\sconnection\sduring\sSELECT\soperation.\sHence\savoiding\susing\sthe\ssame\sconnection\screated\sduring\stable\screation.\r\n\r\nOur\sQuestions:\r\n1.\sWhy\swe\sare\sseeing\sthis\serror\sin\sConsole?\r\n2.\sIs\sthere\sany\sretrying\smechanism\sto\sprepare\sthe\sSQL\sstatement\sin\sSQLite\swhenever\sthis\serror\soccurs?\sThat's\sthe\sreason\sstill\sour\sapplication\sbehaving\sas\sper\sthe\sexpectation.\r\n3.\sHow\scritical\sthis\serror?Do\swe\sneed\sto\signore\sthis\serror?User\sfeels\sbad\sto\ssee\sthis\serror\sin\shis\sconsole.
J login anonymous
J mimetype text/x-markdown
J private_contact 525a262cbcf6f199b6f840881eed74260c051d35
J severity Important
J status Open
J title Database\sSchema\sChanged\sError
J type Question
K b4795f3011238fb1af0737e1195bd327ce7b3897
U anonymous
Z 1667911c6d05444cca647c7540235905
