Thank you Richard.
Do you plan to make a code release or perhaps to release a new code
snapshot, so that I can avoid this situation from happening again?
Regards,
Miroslav
On 14.7.2016. 20:48, Richard Hipp wrote:
This problem is written up in ticket
https://www.sqlite.org/src/tktview/f68
> We change internal-use #defines and other internal-use symbols on just
about
> every release. This has never before caused breakage that we are aware
of.
> Or if it has caused breakage, the developers doing such things are aware
that
> what they are doing is not allowed and have the good sense t
Dear Mr William:
It has been implemente an app with two programs: SQLiteToExcel and
ExcelToSQLite. If you are interested, please, write to me. The Manual is
spanish written.
Yours
Ing. Héctor F. Fiandor Rosario
___
sqlite-users mailing list
sqlite-user
I've reproduced the issue using both SERIALIZED and MULTITHREADED modes.
The issue here doesn't seem to have anything to do with the threading
modes. The issue is related to shared caches, and waiting on a b-tree lock
while holding the global SQLITE_MUTEX_STATIC_OPEN lock.
- Brian Vincent
On Sa
This problem is written up in ticket
https://www.sqlite.org/src/tktview/f68bf68513a1
Short answer: Simply run REINDEX to clear the problem
On 7/13/16, Miroslav Rajcic wrote:
> I am using sqlite to implement document file format in my program.
> I got a document file (sqlite database) from user
Thank you Simon,
tried that, but nothing was reported as faulty whatsoever, for any of
the command that corrupted the database.
The same integrity check reports issues in another script that tests the
database on subsequent load.
I will now send data and a recipe to Richard.
Regards,
Mi
On Thu, Jul 14, 2016 at 9:38 AM, Simon Slavin wrote:
>
> On 14 Jul 2016, at 12:44pm, Igor Korot wrote:
>
>> Is there anything else to check?
>
> No. Those look correct. You looked at the right place and it had the right
> options selected.
>
> Although the SQLite team goes to some lengths to a
On 14 Jul 2016, at 12:44pm, Igor Korot wrote:
> Is there anything else to check?
No. Those look correct. You looked at the right place and it had the right
options selected.
Although the SQLite team goes to some lengths to avoid errors which prevent
compilation, trying to get rid of every
Hi,
On Thu, Jul 14, 2016 at 8:05 AM, Richard Hipp wrote:
> On 7/14/16, wu tao wrote:
>> I tried to do the sqlite db PRAGMA via c-interface, sqlite3_exec() with the
>> following statements,
>>
>> PRAGMA main.cache_size=5000;PRAGMA main.page_size = 2048;PRAGMA
>> main.locking_mode=NORMAL ;PRAGMA m
On 7/14/16, wu tao wrote:
> I tried to do the sqlite db PRAGMA via c-interface, sqlite3_exec() with the
> following statements,
>
> PRAGMA main.cache_size=5000;PRAGMA main.page_size = 2048;PRAGMA
> main.locking_mode=NORMAL ;PRAGMA main.synchronous=NORMAL;PRAGMA
> main.journal_mode=wal;
>
> Looks s
On 7/13/16, William De Luca wrote:
> Hey all,
>
> I am wondering if anyone knows some parameter I can use that will allow a
> CSV import to skip unique entries instead of bailing on the whole process.
>
Import into a TEMP table with no constraints. Then move from the TEMP
table into your real ta
I tried to do the sqlite db PRAGMA via c-interface, sqlite3_exec() with the
following statements,
PRAGMA main.cache_size=5000;PRAGMA main.page_size = 2048;PRAGMA
main.locking_mode=NORMAL ;PRAGMA main.synchronous=NORMAL;PRAGMA
main.journal_mode=wal;
Looks some PRAGMA are set, cache_size setting do
Hey all,
I am wondering if anyone knows some parameter I can use that will allow a CSV
import to skip unique entries instead of bailing on the whole process.
I am writing a script that will use SQLite3 and do many CVS imports that are
guaranteed to have duplicates. I was hoping that after creat
Simon,
On Wed, Jul 13, 2016 at 11:51 PM, Simon Slavin wrote:
>
> On 14 Jul 2016, at 4:43am, Igor Korot wrote:
>
>> Right now my C Language option on the Xcode 5.1.1 is set to "GNU99".
>> When using this option I am getting a lot of different warnings like:
>>
>> Value Conversion Issue
>> Implici
On 14 Jul 2016, at 6:37am, Miroslav Rajcic wrote:
> Good news: actually those SQL commands perfectly reproduce the issue, I just
> forgot to reload the database before checking the issue with "SELECT" query.
We'd like your help identifying the specific line which causes the problem.
Please a
On 7/14/16, Darren Duncan wrote:
>
> My recommendation on this matter is to deprecate but retain the current
> include
> guards that are in violation of the standard, and ALSO add new, redundant
> include guards in a manner that comply with the standard.
>
> Thoughts on that proposal?
>
We change
On 12/07/2016 22:01, Richard Hipp wrote:
OK. Another fix. Please try the latest trunk version.
This version works for me. Thanks.
Nick
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailma
17 matches
Mail list logo