[sqlite] 1st Call For Papers - 23rd Annual Tcl/Tk Conference (Tcl'2016)

Hello SQLite Users, fyi ... 23rd Annual Tcl/Tk Conference (Tcl'2016) http://www.tcl.tk/community/tcl2016/ November 14 - 18, 2016 Crowne Plaza Houston River Oaks 2712 Southwest Freeway, 77098 Houston, Texas, USA Important Dates: Abstracts and proposals due September 12, 2016 Notification to

[sqlite] Compiling SQLite dll 64 bits in MSVS

I said that wrong, even in the old 32 bits Dependency Walker there is nil in the top right pane. Still, there are no decorated function names in the 64 bit dll to see. Is this normal or do I have to alter my command line parameters? RBS On Tue, Apr 5, 2016 at 10:23 PM, Bart Smissaert wrote: >

[sqlite] Compiling SQLite dll 64 bits in MSVS

Thanks, that V2.2 works. What is strange though is that I see nil in the top right pane, so decorated function names. Is this different in the 64 bits dll? RBS On Tue, Apr 5, 2016 at 10:03 PM, GB wrote: > Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have > problems with

[sqlite] Compiling SQLite dll 64 bits in MSVS

I am not using .def files, but use commandline settings from VS: All options: /GS /TC /W3 /Zc:wchar_t /Zi /Gm- /O2 /Fd"x64\Release\vc120.pdb" /fp:precise /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_USRDLL" /D "SQLITE3_STDCALL_EXPORTS" /D "_WINDLL" /errorReport:prompt /WX- /Zc:forScope /Gz /MD

[sqlite] Compiling SQLite dll 64 bits in MSVS

Dependency Walker comes in two different flavors, one for x86 and one for x64. You need to use the appropriate one for your DLL. Bart Smissaert schrieb am 05.04.2016 um 09:50: > Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation. > Using instructions from: > >

[sqlite] Compiling SQLite dll 64 bits in MSVS

I downloaded the 64 bit version of DependencyWalker from here: https://support.microsoft.com/en-us/kb/256872 but it didn't run on my machine although it is Win 7 Pro 64 bits. Will have a look on the MSVS 2013 installation disc. RBS On Tue, Apr 5, 2016 at 8:17 PM, GB wrote: > Dependency

[sqlite] regression in 3.12.0 vs. 3.11.0, column type information in PRAGMA missing

Hello, On 2016-04-05 19:19, Richard Hipp wrote: > Please explain why you think it is important to know the "type" of a > column in a view? For the same reason as it is important in case of a table. Both could be consistent. > There are further inconsistencies here. Example: > > CREATE

[sqlite] sqlite3_column_decltype change

On Tue, Apr 5, 2016 at 8:00 PM, Igor Korot wrote: > On Tue, Apr 5, 2016 at 1:57 PM, L?szl? B?sz?rm?nyi (GCS) > wrote: >> It seems sqlite3_column_decltype() is changed in 3.12.0 without >> mentioning it in the changelog. A test case is attached. > There is no attachment here. > Can you just post

[sqlite] sqlite3_column_decltype change

Hi, It seems sqlite3_column_decltype() is changed in 3.12.0 without mentioning it in the changelog. A test case is attached. Using 3.11.1, the result is not quoted, with 3.12.0 it is. As such, the former outputs: type:json text value:bar; while with the latter prints: type:'json text' value:bar.

[sqlite] SQLITE_IOERR_ACCESS with 3rd party DLL

My code is pretty straight forward.. it simply opens the database and tries to see if a table exists? m_bdbIsOpen and m_bInMemory are both false (so the db is opened okay). You'll notice I don't get an error at sqlite3_exec() in the open method... bool CDatabase::doesTableExist (const

[sqlite] sqlite3_column_decltype change

On 5 Apr 2016, at 7:05pm, L?szl? B?sz?rm?nyi (GCS) wrote: > Checked my sent mail, the attachment is there. Does the list software > delete those? Yes. We don't want everyone sending us their homework. Thanks for posting your file as text. Simon.

[sqlite] SQLITE_IOERR_ACCESS with 3rd party DLL

Oh -- and the database opens fine -- it only fails when I try and call sqlite3_prepare_v2() to check if a table exists in the database sql = pragma table_info('mytablename'); ... it returns with the SQLITE_IOERR_ACCESS error. So the file exists and is good. If I recompile without the 3rd

[sqlite] SQLITE_IOERR_ACCESS with 3rd party DLL

Hi Simon, Thanks for replying. To clarify -- if I run this configuration with the 3rd party LIB I get the error. If I run my program (DLL) without the 3rd party LIB my database works perfectly fine -- so the disk isn't corrupted and the database itself is fine. It's only while running my

[sqlite] SQLITE_IOERR_ACCESS with 3rd party DLL

So I statically compile Sqlite3 version 3.8.7.2 into my DLL using /MT I use #define SQLITE_THREADSAFE 1 #define HAVE_USLEEP 1 When I use my DLL it works perfectly fine? However... If I add a 3rd party LIB which also has Sqlite3 version 3.6.23.1 (I believe) statically linked into it (also

[sqlite] regression in 3.12.0 vs. 3.11.0, column type information in PRAGMA missing

If this change also applies to?sqlite3_table_column_metadata()'s behavior with views, then I would consider it a real negative. ?Currently I can get my declaration types using that call, which are hints on how to interpret the values in the databases I create, from simple views which is

[sqlite] regression in 3.12.0 vs. 3.11.0, column type information in PRAGMA missing

Hello, On 2016-04-05 17:05, Mike Bayer wrote: > OK...so *that* is a change. Is *that* by design, and if so should that > be described here http://sqlite.org/releaselog/3_12_0.html ? I hope that is by an accident. While info about ``notnull'' and ``defaultvalue'' (which is not carried in 3.11.x

[sqlite] FOREIGN KEY constraint failed

Are we confusing immediate constraints (checked per statement) with DEFERRED constraints (checked at COMMIT time) again? > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of R Smith > Sent:

[sqlite] regression in 3.12.0 vs. 3.11.0, column type information in PRAGMA missing

Hello, On 2016-04-04 22:14, Mike Bayer wrote: > if it is by design that views no longer carry typing information, this > is a major behavioral change and no mention of it occurs in the release > notes for 3.12.0, so at the very least this change should be documented > if expected. This is not

[sqlite] regression in 3.12.0 vs. 3.11.0, column type information in PRAGMA missing

On 04/05/2016 01:19 PM, Richard Hipp wrote: > On 4/4/16, Mike Bayer wrote: >> The "type" column in PRAGMA table_info() is now a blank string when the >> target object is a view in 3.12.0. In 3.11.0 and prior versions, the >> typing information is returned, >> > > This could easily be considered

[sqlite] Compiling SQLite dll 64 bits in MSVS

On Tue, Apr 5, 2016 at 2:09 PM, Bart Smissaert wrote: > I am not using .def files, but use commandline settings from VS: > > All options: > > /GS /TC /W3 /Zc:wchar_t /Zi /Gm- /O2 /Fd"x64\Release\vc120.pdb" /fp:precise > /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_USRDLL" /D >

[sqlite] Compiling SQLite dll 64 bits in MSVS

def files are obsolete. the instructions include setting SQLITE_API to __declspec(dllexport) which should do the job... unless there was a typeo On Tue, Apr 5, 2016 at 2:03 PM, GB wrote: > Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have > problems with post-XP OS. Try V2.2

[sqlite] sqlite3_column_decltype change

Hi, On Tue, Apr 5, 2016 at 1:57 PM, L?szl? B?sz?rm?nyi (GCS) wrote: > Hi, > > It seems sqlite3_column_decltype() is changed in 3.12.0 without > mentioning it in the changelog. A test case is attached. Using 3.11.1, > the result is not quoted, with 3.12.0 it is. > As such, the former outputs:

[sqlite] FOREIGN KEY constraint failed

Thank you for reply ! Yes you are right in most of your points. The code overhead/footprint can be inside preprocessor macros and we can have for development as we normally do a build with debug ON so in production there will be nothing new. Throwing a bunch of false positives to

[sqlite] regression in 3.12.0 vs. 3.11.0, column type information in PRAGMA missing

On 4/4/16, Mike Bayer wrote: > The "type" column in PRAGMA table_info() is now a blank string when the > target object is a view in 3.12.0. In 3.11.0 and prior versions, the > typing information is returned, > This could easily be considered a bug fix rather than a regression. Please explain why

[sqlite] FOREIGN KEY constraint failed

On 2016/04/04 10:43 PM, Domingo Alvarez Duarte wrote: > Thanks for reply ! > > I already sent a proposal to Richard to add a pragma "PRAGMA DEBUG_MODE" and > when set throw any kind of error to stderr/sqlite3_(hook) this way ther is no > need to store temporary conditions to show later. > > And

[sqlite] Using index in sqlite

On 2016/04/05 12:01 PM, jose.campos.romero at andaluciajunta.es wrote: > Hello > > If I create an index for a table, when an application accesses the table, > Sqlite automatically will use the index when necessary? > > Thanks in advance Yes, whenever possible.

[sqlite] Using index in sqlite

Hello If I create an index for a table, when an application accesses the table, Sqlite automatically will use the index when necessary? Thanks in advance

[sqlite] How to order by absolute value ?

On 2016/04/05 11:48 AM, Niall O'Reilly wrote: > On 5 Apr 2016, at 10:06, Graham Holden wrote: > >> Change "select abs(num)" in your second example to "select num" and >> you should be good. I'm guessing in your first example the ORDER BY >> only applies to the last SELECT. > > I expect

[sqlite] How to order by absolute value ?

On 5 Apr 2016, at 10:59, R Smith wrote: > > The documentation is correct and the fault is not that the ORDER BY > did not only apply to the last select - the problem is more that the > ORDER BY abs(num) did not know that "num" is a valid column name in > the compound select - which seems

[sqlite] How to order by absolute value ?

? Thank you for reply ! Yes it works ! > Tue Apr 05 2016 11:06:52 AM CEST from "Graham Holden" > Subject: Re: [sqlite] How to order by absolute >value >? > > Change "select abs(num)" in your second example to "select num" and you >should be good. I'm guessing in your first example the

[sqlite] How to order by absolute value ?

Thank you for reply ! Yes it works ! > Tue Apr 05 2016 11:12:03 AM CEST from "R Smith" >Subject: Re: [sqlite] How to order by absolute value ? > > On 2016/04/05 10:47 AM, Domingo Alvarez Duarte wrote: > >>Hello ! >> >> I want to achieve this: >> >> select 1 as num >> union >> select 3

[sqlite] How to order by absolute value ?

On 2016/04/05 10:47 AM, Domingo Alvarez Duarte wrote: > Hello ! > > I want to achieve this: > > select 1 as num > union > select 3 as num > union > select -2 as num > > order by abs(num) -- result [1, -2, 3] > > But it doesn't work this works but doesn't show what I want: > > select abs(num) >

[sqlite] regression in 3.12.0 vs. 3.11.0, column type information in PRAGMA missing

On 04/05/2016 10:43 AM, Cezary H. Noweta wrote: > > IMHO, this described by you behavior can be considered as a bug in > ``PRAGMA table_info'', which takes column's affinity from ``CREATE > TABLE'' command only as for now. OK...so *that* is a change. Is *that* by design, and if so should that

[sqlite] How to order by absolute value ?

On 5 Apr 2016, at 10:06, Graham Holden wrote: > Change "select abs(num)" in your second example to "select num" and > you should be good. I'm guessing in your first example the ORDER BY > only applies to the last SELECT. I expect you're right, but https://www.sqlite.org/lang_select.html

[sqlite] How to order by absolute value ?

Hello ! I want to achieve this: select 1 as num union select 3 as num union select -2 as num order by abs(num) -- result [1, -2, 3] But it doesn't work this works but doesn't show what I want: select abs(num) from ( select 1 as num union select 3 as num union select -2 as num ) order

[sqlite] How to order by absolute value ?

Change "select abs(num)" in your second example to "select num" and you should be good. I'm guessing in your first example the ORDER BY only applies to the last SELECT. Graham. Sent from Samsung Mobile Original message From: Domingo Alvarez Duarte

[sqlite] Compiling SQLite dll 64 bits in MSVS

Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation. Using instructions from: http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php All compiles well, so no warnings and get a dll of about 700 kB. Nil shows

[sqlite] FOREIGN KEY constraint failed

On Mon, 04 Apr 2016 17:51:30 +0200 Domingo Alvarez Duarte wrote: >FOREIGN KEY constraint failed >I have some databases with lots of foreign keys and I sometimes I need to >change the structure of some tables and I get this message Before restructuring a database schema always use: PRAGMA

[sqlite] Error help

>> I was taught the basics in SQLite with Firefox, and >> am already disappointed that I can't really do what I want to do with the >> Firefox plug in. > Plenty of other ways to use SQLite with a graphical GUI: > > > >