[Gambas-user] Issue 317 in gambas: sqlite3 INTEGER type does not appear to be supported correctly

[gambas at ...2524...]

Status: New
Owner: ----
Labels: Version-3.2.0 Type-Bug Priority-Medium OpSys-Any Dist-Any Arch-Any  
Desktop-Any GUI-Any

New issue 317 by ron.mcin... at ...626...: sqlite3 INTEGER type does not  
appear to be supported correctly
http://code.google.com/p/gambas/issues/detail?id=317

1) Describe the problem.
When using an externally defined sqlite3 DB types declared as "INTEGER" do  
not function correctly whereas types declared as INT4 do. Performing an  
assignment into a field of type "INTEGER" does not work (and does not raise  
any exception) i.e. the field remains null after an apparently successful  
assignment.

2) GIVE THE FOLLOWING INFORMATIONS (if they are appropriate):

Version: 3.2.1
Operating system: Linux
Distribution: Mint MDE (Debian based)
Architecture: x86
GUI component: N/A
Desktop used: Gnome

3) Provide a little project that reproduces the bug or the crash.
Attached.

4) If your project needs a database, try to provide it, or part of it.
Tested using a small sqlite3 DB (generated from the command line version of  
sqlite3 using the following SQL code).

DROP TABLE IF EXISTS "test";
CREATE TABLE "test" ("id" INTEGER PRIMARY KEY  NOT NULL , "num" INTEGER NOT  
NULL , "test" TEXT, "idn" INTEGER, "idn4" INT4);

test.sqlite and test.sql are located in the projects home directory.

5) Explain clearly how to reproduce the bug or the crash.
Run the project which will fail on the DB update and allow you to verify  
that the idn field remains null whilst the idn4 field has been updated.



Attachments:
	DemoError.tar.gz  5.8 KB