Re: [sqlite] Bug in trigger: when comparing a value of an int column to a quoted value

2011-12-24 Thread romtek
So, you also think this is a bug? I will submit it to the SQLite bug database.


On Wed, Dec 21, 2011 at 7:42 AM, Alexey Pechnikov
 wrote:
> The problem can be fixed by variables bindings patch:
> http://sqlite.mobigroup.ru/wiki?name=tclsqlite
> I think, you can do same for you lang.
>
> --
> Best regards, Alexey Pechnikov.
> http://pechnikov.tel/
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] library routine called out of sequence

2011-12-24 Thread Tito Ciuro
Hi Sreekumar,

Do you have a db connection shared across threads? This is not advised . Try 
opening a db connection per thread instead.

-- Tito

On Dec 23, 2011, at 15:06, Sreekumar TP  wrote:

> Hi,
> 
> yes, I know. I have a multithreaded app. One db conection.I will try to
> reproduce the problem with a simple app.
> 
> However, the difference between the working and non working case is that in
> the working case statements are prepared each time. In the non working
> case, its reused.
> 
> The very first call to bind throws this error.
> 
> Sreekumar
> On Dec 23, 2011 2:51 PM, "Pavel Ivanov"  wrote:
>> 
>> Devil is in the details. What you described in general is okay. But I
>> guess the exact code you have has some problems. To find them we
>> should see the code.
>> 
>> An just some first check: do you have a single-threaded application
>> accessing database?
>> 
>> 
>> Pavel
>> 
>> 
>> On Fri, Dec 23, 2011 at 3:32 AM, Sreekumar TP 
> wrote:
>>> Hi ,
>>> 
>>> I have a strange problem. I do the following in sequence -
>>> 
>>> 1. open database
>>> 2. set pragmas
>>> 3.create table
>>> 4. prepare a paremetrised statement ( SELECT ..)
>>> 5. bind values to the statement
>>> 6. step
>>> 
>>> At 5, I get the error  "library routine called out of sequence".
>>> 
>>> If I replace the parameterised statement  with a 'non-parameterised'
>>> statement, I have no issues.
>>> 
>>> If I use a parameterized INSERT statement , I do not get the error.
>>> 
>>> Any suggestions?
>>> 
>>> -Sreekumar
>>> ___
>>> sqlite-users mailing list
>>> sqlite-users@sqlite.org
>>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>> ___
>> sqlite-users mailing list
>> sqlite-users@sqlite.org
>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] sqlite3_column_text() returning partial results

2011-12-24 Thread Tony McC
On Wed, 21 Dec 2011 21:33:02 +
"Jacob A. Camp"  wrote:

> There it is, when I printed this value out to a txt file everything
> was there. 
> 
> Apparently there is some sort of character limit when displaying
> strings in debug mode in Visual Studio 2010, news to me...
> 
> Thanks everyone!

That's what the 2010 in the name of the product means: displayed strings
are limited to that many characters (Studio is an acronym meaning Stop
Displaying Under Debugger If Over [2010]). You were lucky to get a few
more, but that is undocumented behaviour.  If you upgrade next year
though you should be able to display a couple more characters.

Tony
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users