[sqlite] In the case of ZIPVFS

Thank you very much. At 2015-12-23 17:32:26, "Richard Hipp" wrote: >On 12/23/15, ??? <2004wqg2008 at 163.com> wrote: >> HI,all >> SQLite retrieves the compressed records is slower than the uncompressed >> records about 30%. >> How can improve the problem? and anyone any suggustion? >>

[sqlite] whish list for 2016

I would like a less limited 'alter table' statement, to be able to drop columns and to add columns at a position of my own choice instead of always at the end.

[sqlite] Malloc getting segmentation fault in sqlite

Hi All, I am working on Sqlite in multi threaded environment on ARM v7 platform. I am facing problems with malloc() function returning segmentation fault. The problem is not frequent but out of 100 times am getting this once. The backtrace is pasted below. (gdb) bt #0 0x4038eb18 in malloc ()

[sqlite] whish list for 2016

On Thu, Dec 24, 2015 at 6:49 AM, gunnar wrote: > I would like a less limited 'alter table' statement, to be able to drop > columns and to add columns at a position of my own choice instead of always > at the end. > > ?I'm curious as to why. Doing so would, most likely, require rewriting the

[sqlite] whish list for 2016

On Thu, Dec 24, 2015 at 1:12 PM, John McKown wrote: > > On Thu, Dec 24, 2015 at 6:49 AM, gunnar wrote: > > > I would like a less limited 'alter table' statement, to be able to drop > > columns and to add columns at a position of my own choice instead of always > > at the end. > > > > > I'm

[sqlite] Malloc getting segmentation fault in sqlite

Yes when I free'd memory I shouldn't have and kept a reference to it in other places... or that after freeing I had modified memory. But not from sqlite itself. On Thu, Dec 24, 2015 at 2:02 AM, santosh dasimanth wrote: > Hi All, > I am working on Sqlite in multi threaded environment on ARM v7

[sqlite] Malloc getting segmentation fault in sqlite

On 12/24/2015 05:02 PM, santosh dasimanth wrote: > Hi All, > I am working on Sqlite in multi threaded environment on ARM v7 platform. > > I am facing problems with malloc() function returning segmentation fault. > The problem is not frequent but out of 100 times am getting this once. > > The

[sqlite] whish list for 2016

On 24 Dec 2015, at 3:12pm, John McKown wrote: > ?I'm curious as to why. Doing so would, most likely, require rewriting the > entire table. If you want a SELECT * to get the columns in a particular > order, just create a VIEW with the columns in the order in which you want > them. I think

[sqlite] wish list for 2016

On 24 Dec 2015 at 15:26, Bernardo Sulzbach wrote: > want a more versatile alter table for convenience. However, I don't > know if alter table is used at all in production anywhere (why would > it be? the column names and ordering should not be part of the data). If I distribute an app with a

[sqlite] wish list for 2016

On Thu, Dec 24, 2015 at 2:30 PM, Tim Streater wrote: > On 24 Dec 2015 at 15:26, Bernardo Sulzbach > wrote: > >> want a more versatile alter table for convenience. However, I don't >> know if alter table is used at all in production anywhere (why would >> it be? the column names and ordering

[sqlite] whish list for 2016

On Thu, Dec 24, 2015 at 10:14 AM, Simon Slavin wrote: > > On 24 Dec 2015, at 3:12pm, John McKown > wrote: > > > ?I'm curious as to why. Doing so would, most likely, require rewriting > the > > entire table. If you want a SELECT * to get the columns in a particular > > order, just create a VIEW

[sqlite] whish list for 2016

On 12/24/15 10:26 AM, Bernardo Sulzbach wrote: > I think you focused too much on the ordering issue. He or she may > just > want a more versatile alter table for convenience. However, I > don't know if alter table is used at all in production anywhere (why > would it be? the column names and

[sqlite] whish list for 2016

On 24 Dec 2015, at 5:10pm, Richard Damon wrote: > being able to directly add a field would be nice. You can directly add a field. Simon.

[sqlite] whish list for 2016

On Thu, Dec 24, 2015 at 3:10 PM, Richard Damon wrote: > On 12/24/15 10:26 AM, Bernardo Sulzbach wrote: >> >> I think you focused too much on the ordering issue. He or she may > just >> want a more versatile alter table for convenience. However, I > > > don't know if alter table is used at all

[sqlite] whish list for 2016

On Thu, Dec 24, 2015 at 3:16 PM, Simon Slavin wrote: > > On 24 Dec 2015, at 5:10pm, Richard Damon wrote: > >> being able to directly add a field would be nice. > > You can directly add a field. > > > > Simon. Good catch, you cannot place it wherever

[sqlite] whish list for 2016

On 12/24/15 12:17 PM, Bernardo Sulzbach wrote: > Interesting. I suppose that most of this "table editing" should rely > on an > abstraction layer anyway: think about supporting other RDBMS in > the future. However, I recognize that in your case a more capable > alter table may simplify things

[sqlite] whish list for 2016

On Dec 24, 2015, at 9:14 AM, Simon Slavin wrote: > > ALTER TABLE DROP COLUMN ... > > ...the way SQLite3 is written makes it difficult or inefficient to implement > them. I wouldn?t mind if SQLite did nothing more than the recommended manual process for emulating the ALTER TABLE affordances

[sqlite] whish list for 2016

On Dec 24, 2015, at 8:26 AM, Bernardo Sulzbach wrote: > > I don't > know if alter table is used at all in production anywhere (why would > it be? the column names and ordering should not be part of the data). Requirements change. In the past dozen years, the database schema I?m working on

[sqlite] Malloc getting segmentation fault in sqlite

I am interested in this as I have bug that I am sure is to do with some sort of memory problem. It only occurs when I run a procedure defined with sqlite3_create_function. This procedure is not in sqlite3.dll but in a VB6 ActiveX dll. I use the unaltered Windows sqlite3.dll. My question is if

[sqlite] whish list for 2016

On Dec 24, 2015, at 11:17 AM, Warren Young wrote: > > BEGIN TRANSACTION; > ALTER TABLE Foo RENAME TO oldFoo; > CREATE TABLE Foo ? a bunch of repeated stuff >? almost identical to the initial >? DBMS creation code with just one >?

[sqlite] Malloc getting segmentation fault in sqlite

On 12/24/15, Bart Smissaert wrote: > My question is if there is ever any need in this situation to run one of > the sqlite3 memory procedures, that is > sqlite3_free, sqlite3_malloc or sqlite3_realloc? > Currently I am not using this anywhere in my VB6 code. > Should I? Cases when you might use

[sqlite] Malloc getting segmentation fault in sqlite

OK, thanks I don't use any of 1 to 3, I only use the standard SQLite functions such as sqlite3_open_v2, sqlite3_prepare16_v2, sqlite3_step, sqlite3_bind, sqlite3_column, sqlite3_create_function_v2, sqlite3_finalize, sqlite3_reset, sqlite3_result, sqlite3_value and qlite3_close. So, in that case I

[sqlite] whish list for 2016

Hi, better ALTER command would be very welcome. e.g. RENAME/DELETE column or field. Instead of us writing code to do it, it could be a command where SQLite does things right. Sincerely Christian -- Read our blog about news on our plugins: http://www.mbsplugins.de/

[sqlite] Malloc getting segmentation fault in sqlite

On 24 Dec 2015, at 9:10pm, Bart Smissaert wrote: > Given that I don't use theses it then likely that my problem is to do with > a buffer overwrite? You say you use sqlite3_bind(). See the details about the fifth parameter in A common mistake is

[sqlite] Malloc getting segmentation fault in sqlite

I have no problems at all with sqlite3_bind, but I understand that the sqlite3_result group of procedures is very similar to sqlite3_bind group. In a UDF procedure (callback procedure in the ActiveX dll) I do things like this: sqlite3_result_text lPtr_ObjContext, VarPtr(arrBytes1(0)), lPos - 1,

[sqlite] Malloc getting segmentation fault in sqlite

On 12/24/15, Bart Smissaert wrote: > I have no problems at all with sqlite3_bind, but I understand that the > sqlite3_result group of procedures is very similar to sqlite3_bind group. > > In a UDF procedure (callback procedure in the ActiveX dll) I do things like > this: > > sqlite3_result_text

[sqlite] whish list for 2016

Two parter; *Part 1;* One thing I would suggest, if you're looking to add and delete columns dynamically is not to worry about the order of the columns in the database, but, have a second table hanging around that remembers the specified order the user wants to see the columns in. Doing your

[sqlite] whish list for 2016

On Thu, Dec 24, 2015 at 4:09 PM, Christian Schmitz < realbasiclists at monkeybreadsoftware.de> wrote: > Hi, > > better ALTER command would be very welcome. > > e.g. RENAME/DELETE column or field. > ?RENAME exists.? ?ALTER TABLE table-name RENAME COLUMN column_field_name TO

[sqlite] whish list for 2016

On 12/24/15, John McKown wrote: > > DELETE is normally done as: ALTER TABLE table-name DROP ?COLUMN > column_file_name; and would be a very nice addition. I hadn't noticed that > it is missing. I wonder why. Perhaps Dr. Hipp will comment after the > holidays. > Merry Christmas. DROP COLUMN and

[sqlite] whish list for 2016

On Thu, Dec 24, 2015 at 8:39 PM, Simon Slavin wrote: > > On 25 Dec 2015, at 2:35am, Bernardo Sulzbach > wrote: > > >> ALTER TABLE table-name RENAME COLUMN column_field_name TO > >> new_column_field_name; > > > > Are you sure? The documentation does not have anything about this and > > I get a

[sqlite] Malloc getting segmentation fault in sqlite

It's been quite a long while since I used vb6 on a regular basis; however, integrating with native DLLs can be quite tricky for several reasons: 1. It cannot call any native function that does not conform to the "stdcall" calling convention. 2. It has a very Win32-centric way of marshalling