Re: [sqlite] [patch] for test/backup2.test

[jungle boogie]

Hi All,
On 07/06/2017 10:51 PM, Pavel Volkov wrote:

Hello.
Please, make test 'test/backup2.test' more compatible with FreeBSD.
This is patch for it:

--- test/backup2.test.orig  2017-07-07 04:59:34 UTC
+++ test/backup2.test
@@ -143,7 +143,7 @@ do_test backup2-9 {
  #
  if {$tcl_platform(platform)=="windows"} {
set msg {cannot open source database: unable to open database file}
-} elseif {$tcl_platform(os)=="OpenBSD"} {
+} elseif {$tcl_platform(os)=="OpenBSD"||$tcl_platform(os)=="FreeBSD"} {
set msg {restore failed: file is encrypted or is not a database}
  } else {
set msg {cannot open source database: disk I/O error}



Any chance of this patch getting accepted/reviewed?

Without it, this happens:
Time: backcompat.test 13 ms 




! backup2-10 expected: [1 {cannot open source database: disk I/O error}] 




! backup2-10 got:  [1 {restore failed: file is not a database}]




Thank you.

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

Re: [sqlite] Example/recipe for truncating fp numbers

[Keith Medcalf]

Though I would use:

  trunc(value * pow(10, places)) / pow(10, places)

so that all the operations are performed using full floating point, but then I 
have the whole math library loaded into SQLite3 ...

I just added an override for the math library trunc function that takes two 
arguments so you can do:

  trunc(value, 3)

which does the truncation (towards 0) and maintains precision.

On the other hand, I have never seen any need to truncate a floating point 
number, though there are many times when one needs to apply proper rounding 
(half-to-even) for which I have written a "roundhe" function ...

Truncation or rounding of course only *ever* applied to "display to user and 
discarded" results and never ever applied to intermediates or stored so having 
the ability to do this inside the SQLite engine rather than at the application 
level is of dubious value ... other than if you need to keep a log or something 
that does not participate in further calculations.

Here is the roundhe function to do statistical / stochastic / bankers' / 
half-even rounding:

/*
** Define a Statistical (Gaussian/Bankers) rounding function
**
** Round < 0.5 towards zero
**   = 0.5 towards even
**   > 0.5 away from zero
**
** Implements recommended IEEE round-half-even
*/

SQLITE_PRIVATE void _heroundingFunc(sqlite3_context *context, int argc, 
sqlite3_value **argv)
{
int p = 0;
double x, scale, xval, ipart, fpart, sgn;

if ((argc == 0) || (argc > 2))
return;
if (sqlite3_value_type(argv[0]) == SQLITE_NULL)
return;
x = sqlite3_value_double(argv[0]);
if (argc == 2)
{
if (sqlite3_value_type(argv[1]) == SQLITE_NULL)
return;
p = sqlite3_value_int(argv[1]);
p = p > 15 ? 15 : (p < 0 ? 0 : p);
}
scale = pow(10.0, p);
sgn = 1.0;
if (x < 0)
sgn = -1.0;
xval = sgn * x * scale;
if (log10(xval) > 16.0)
{
sqlite3_result_double(context, x);
return;
}
fpart = modf(xval, );
if ((fpart > 0.5) || ((fpart == 0.5) && (fmod(ipart, 2.0) == 1.0)))
ipart += 1.0;
xval = sgn * ipart / scale;
sqlite3_result_double(context, xval);
}

and I just added one that truncates without rounding:

/*
** Define a floating point truncation function that allows truncation to some 
number of decimal places
** Retains 1 ulp precision
*/

SQLITE_PRIVATE void _fptruncateFunc(sqlite3_context *context, int argc, 
sqlite3_value **argv)
{
int p = 0;
double x, scale, xval, ipart, fpart, sgn;

if ((argc == 0) || (argc > 2))
return;
if (sqlite3_value_type(argv[0]) == SQLITE_NULL)
return;
x = sqlite3_value_double(argv[0]);
if (argc == 2)
{
if (sqlite3_value_type(argv[1]) == SQLITE_NULL)
return;
p = sqlite3_value_int(argv[1]);
}
scale = pow(10.0, p);
sgn = 1.0;
if (x < 0)
sgn = -1.0;
xval = sgn * x * scale;
fpart = modf(xval, );
xval = sgn * ipart / scale;
sqlite3_result_double(context, xval);
}

 
> Why not just use:
> 
>   cast(value * 1000 as integer) / 1000.0
> 
> 
> > Hello,
> >
> > Below is a recipe on a "best effort" basis, to truncate fp numbers on
> > the right side of the decimal separator with SQLite.
> >
> > It is not intended to correct any fp numbers processing, but only to
> > discard, without any rounding, unwanted fractional digits.
> >
> > The following is directed to discard all digits of a number after the
> > third fractional position (slight and easy adjustments must be done for
> > different positional truncations) :
> >
> >  round(  CAST(/expression/ AS INTEGER)
> >
> >+ /((expression/  * 1000 % 1000 ) / 1000 ), 3)
> >
> > (round() is used against eventually imprecise representation resulting
> > from the top level addition operation)
> >
> > Caveat : force an eventual INTEGER representation resulting from
> > /expression/ to its equivalent REAL representation (ie : x -> x.0)
> >
> > (not a pb for me)
> >
> > Improvements/comments welcome (and wil be happy when an equivalent
> > function finds its way into SQLite)
> >
> > Thanks.
> >
> > -jm
> >
> >
> >
> >
> >
> >
> > ---
> > L'absence de virus dans ce courrier électronique a été vérifiée par le
> > logiciel antivirus Avast.
> > https://www.avast.com/antivirus
> > ___
> > sqlite-users mailing list
> > sqlite-users@mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



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

Re: [sqlite] Example/recipe for truncating fp numbers

[Richard Hipp]

On 7/10/17, Jean-Marie CUAZ  wrote:
> Hello,
>
> Below is a recipe on a "best effort" basis, to truncate fp numbers on
> the right side of the decimal separator with SQLite.

I don't understand how this is different from "round(N,3)"?

What are you trying to do to the fp number N that "round(N,3)" does not do?

What am I missing?

>
> It is not intended to correct any fp numbers processing, but only to
> discard, without any rounding, unwanted fractional digits.
>
> The following is directed to discard all digits of a number after the
> third fractional position (slight and easy adjustments must be done for
> different positional truncations) :
>
>  round(  CAST(/expression/ AS INTEGER)
>
>+ /((expression/  * 1000 % 1000 ) / 1000 ), 3)
>
> (round() is used against eventually imprecise representation resulting
> from the top level addition operation)
>
> Caveat : force an eventual INTEGER representation resulting from
> /expression/ to its equivalent REAL representation (ie : x -> x.0)
>
> (not a pb for me)
>
> Improvements/comments welcome (and wil be happy when an equivalent
> function finds its way into SQLite)
>
> Thanks.
>
> -jm
>
>
>
>
>
>
> ---
> L'absence de virus dans ce courrier électronique a été vérifiée par le
> logiciel antivirus Avast.
> https://www.avast.com/antivirus
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>


-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Example/recipe for truncating fp numbers

[Keith Medcalf]

Why not just use:

  cast(value * 1000 as integer) / 1000.0


> Hello,
> 
> Below is a recipe on a "best effort" basis, to truncate fp numbers on
> the right side of the decimal separator with SQLite.
> 
> It is not intended to correct any fp numbers processing, but only to
> discard, without any rounding, unwanted fractional digits.
> 
> The following is directed to discard all digits of a number after the
> third fractional position (slight and easy adjustments must be done for
> different positional truncations) :
> 
>  round(  CAST(/expression/ AS INTEGER)
> 
>+ /((expression/  * 1000 % 1000 ) / 1000 ), 3)
> 
> (round() is used against eventually imprecise representation resulting
> from the top level addition operation)
> 
> Caveat : force an eventual INTEGER representation resulting from
> /expression/ to its equivalent REAL representation (ie : x -> x.0)
> 
> (not a pb for me)
> 
> Improvements/comments welcome (and wil be happy when an equivalent
> function finds its way into SQLite)
> 
> Thanks.
> 
> -jm
> 
> 
> 
> 
> 
> 
> ---
> L'absence de virus dans ce courrier électronique a été vérifiée par le
> logiciel antivirus Avast.
> https://www.avast.com/antivirus
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



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

Re: [sqlite] Example/recipe for truncating fp numbers

[Simon Slavin]

On 10 Jul 2017, at 6:17pm, Jean-Marie CUAZ  wrote:

> Improvements/comments welcome

I would suggest you try an equivalent function, starting by turning the number 
into a string and looking for the decimal point in it.  This may or may not 
work better, but a second way of doing things is always interesting.

>  (and wil be happy when an equivalent function finds its way into SQLite)

As I’m sure you know by now, the developers of SQLite consider that SQLite is 
for store and recall, and that processing should be done by your own code (or 
"awk" or whatever you use).

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

[sqlite] Example/recipe for truncating fp numbers

[Jean-Marie CUAZ]

Hello,

Below is a recipe on a "best effort" basis, to truncate fp numbers on 
the right side of the decimal separator with SQLite.


It is not intended to correct any fp numbers processing, but only to 
discard, without any rounding, unwanted fractional digits.


The following is directed to discard all digits of a number after the 
third fractional position (slight and easy adjustments must be done for 
different positional truncations) :


round(  CAST(/expression/ AS INTEGER)

  + /((expression/  * 1000 % 1000 ) / 1000 ), 3)

(round() is used against eventually imprecise representation resulting 
from the top level addition operation)


Caveat : force an eventual INTEGER representation resulting from 
/expression/ to its equivalent REAL representation (ie : x -> x.0)


(not a pb for me)

Improvements/comments welcome (and wil be happy when an equivalent 
function finds its way into SQLite)


Thanks.

-jm






---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Documentation improvement recommendations

[jungle Boogie]

Here's a couple more.

On this page: https://www.sqlite.org/src/doc/trunk/README.md

describes the LALR(1) grammer
should be:
describes the LALR(1) grammar

Each has a suscinct
should be:
Each has a succinct

-

On this page: https://www.sqlite.org/dbstat.html

The the DBSTAT virtual
should be:
The DBSTAT virtual
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Documentation improvement recommendations

[jungle Boogie]

Hi All,

Here's a list of some documentation improvements.

-

On this page: https://www.sqlite.org/rbu.html

an RBU Vaccum is
should be:
an RBU Vacuum is

What about this change.
Preparing An RBU Update File
To:
Preparing an RBU Update File


Too many words:
it may be be more
should be:
it may be more

-

On this page: https://www.sqlite.org/sqldiff.html

but do not show the actual chagnes
should be:
but do not show the actual changes

(sometimes refered to as "shadow" tables)
should be:
(sometimes referred to as "shadow" tables)

-

On this page: https://www.sqlite.org/copyright.html

Obtaining An License To Use SQLite
should be:
Obtaining A License To Use SQLite

I recommend:
Obtaining a License to Use SQLite

-

On this page: https://www.sqlite.org/faq.html
How do I create an AUTOINCREMENT field.
should be
How do I create an AUTOINCREMENT field?

-

On this page: https://www.sqlite.org/privatebranch.html
You can the create
should be:
You can then create

-
On this page: https://sqlite.org/android/doc/trunk/www/index.wiki

various ways the the SQLite
should be:
various ways the SQLite


Thanks!


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite Port/ODBC Driver Question

[dmp]

Hello Vishal,

As far as I know the Java version of the Werner javasqlite
driver does not use a port and the odbc may not also.

I have use this Java driver, but a more current active
driver project for Java is at GitHub:

https://github.com/xerial/sqlite-jdbc/

As indicated SQLite is local file system database. Though
I have tested the sqlite-jdbc driver on Win with a mapped
network drive. The stability of that mode of operation is
questionable, as can be searched on this forum's discussions.

danap.

> Hi,
> Am trying to open a firewall to the machine having sqlite database. Does
the SQLite
> database use a specific port number ? If not, then does the ODBC
connection to
> SQLite using ODBC driver use a port ?

> Any help will be greatly appreciated.

> SQLite ODBC Driver:
> http://www.ch-werner.de/sqliteodbc/sqliteodbc.exe

> Regards,
> Vishal Shukla

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

Re: [sqlite] VALUES clause quirk or bug?

[David Raymond]

(New changes in testing look good, so sorry if this is reopening this)

If you need column names with a VALUES table, why not just kick the VALUES to 
the front in a CTE where you can name the fields? Then you don't need a temp 
table or temp view that you need to remember to drop, and since you usually 
know what you're putting into the values table right at the start you're not 
gonna be complicating anything with the CTE.


WITH valueTable (c1, c2) AS (values (1, 2), (3, 4))
SELECT custom_aggregate(c1, c2) FROM valueTable;


SQLite version 3.19.3 2017-06-08 14:26:16
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.

sqlite> with valueTable (field1, field2) as (values (1, 2), (3, 4)) select * 
from valueTable;
--EQP-- 0,0,0,SCAN SUBQUERY 1
field1|field2
1|2
3|4
Run Time: real 0.001 user 0.00 sys 0.00

sqlite> with valueTable (field1, field2) as (values (1, 2), (3, 4)) select 
field2, field1 from valueTable;
--EQP-- 0,0,0,SCAN SUBQUERY 1
field2|field1
2|1
4|3
Run Time: real 0.001 user 0.00 sys 0.00

sqlite> with valueTable (c1, c2, c3) as (values (1, 2, 3), (4, 5, 6)) select 
max(c1, c3) from valueTable;
--EQP-- 0,0,0,SCAN SUBQUERY 1
max(c1, c3)
3
6
Run Time: real 0.006 user 0.00 sys 0.00

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

Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

[Simon Slavin]

On 10 Jul 2017, at 9:17am, mohan_gn  wrote:

> Since our product is already in field with older
> version of SQLite, we want to know this bug's impact. We use simple queries
> like 'select * from abc where col1=123 and col2=456'. We don't use any
> JOINs, VIEWs, nested queries. The tables we use do have primary keys and
> foreign keys. 
> So I wanted to know whether in our cases the bug will impact and whether we
> may be affected.

You do not say which version of SQLite your product uses.  If it’s earlier than 
3.7.7 or later than 3.16.2 then it is not affected.

Temporary indexes are made when there is no index ideally suited to your ORDER 
BY and WHERE clauses.  If your queries execute quickly because you have made 
the right indexes then this bug will not affect you.  See section 12.0 of



You can execute each of your SELECT/INSERT/UPDATE/DELETE commands with EXPLAIN 
QUERY PLAN in front of it, and check the output to see if it mentions a 
temporary index:



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

Re: [sqlite] SQLite Port/ODBC Driver Question

[Richard Hipp]

On 7/10/17, Rob Willett  wrote:
>
> A good rule of thumb is to avoid using SQLite in situations where the
> same database will be accessed directly (without an intervening
> application server) and simultaneously from many computers over a
> network."
>

Another way to express this rule-of-thumb:  Move the query to the
data, not the data to the query.

-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite Port/ODBC Driver Question

[Rob Willett]

It depends on what you mean remotely.

By itself SQLite doesn't have any networking library built in. It's an 
embedded database.


You can put application wrappers around the database, I believe that 
wrappers exist to make SQLIte into a true client/server but thats 
additional code. Also there is ODBC, but there's nothing (AFAIK) in the 
actual codebase itself that allows any remote connectivity.


Clearly you can put Apache/Nginx/PHP/SQlite into a software stack and 
make it work, we actually use Nginx/Mojolicious/SQLite as our platform 
stack but there's nothing in there that allows any remote access to 
SQLite.


If you are talking about hosting the database on a network volume, I 
would recommend that you read this


https://sqlite.org/whentouse.html

The very first paragraph states what Sqlite can do. I would also pay 
close attention to
"If there are many client programs sending SQL to the same database over 
a network, then use a client/server database engine instead of SQLite. 
SQLite will work over a network filesystem, but because of the latency 
associated with most network filesystems, performance will not be great. 
Also, file locking logic is buggy in many network filesystem 
implementations (on both Unix and Windows). If file locking does not 
work correctly, two or more clients might try to modify the same part of 
the same database at the same time, resulting in corruption. Because 
this problem results from bugs in the underlying filesystem 
implementation, there is nothing SQLite can do to prevent it.


A good rule of thumb is to avoid using SQLite in situations where the 
same database will be accessed directly (without an intervening 
application server) and simultaneously from many computers over a 
network."


Just my 2p worth,

Rob

On 10 Jul 2017, at 14:14, Igor Korot wrote:


Rob,

On Mon, Jul 10, 2017 at 7:06 AM, Rob Willett
 wrote:

Vishal,

SQLite isn't a traditional client/server relational database, 
therefore

there isn't a port to open up. It runs on a local machine.


I believe SQLite can successfully be run remotely.

Thank you.



Now there are wrappers around SQLite to extend it, I assume this ODBC 
driver

is one of them.

I suspect people here *may* know the answer regarding any ports the 
ODBC
driver uses, but you may be better off asking the maintainer of the 
ODBC

driver.

Rob


On 10 Jul 2017, at 1:31, Shukla, Vishal wrote:


Hi,
Am trying to open a firewall to the machine having sqlite database. 
Does
the SQLite database use a specific port number ? If not, then does 
the ODBC

connection to SQLite using ODBC driver use a port ?

Any help will be greatly appreciated.

SQLite ODBC Driver:
http://www.ch-werner.de/sqliteodbc/sqliteodbc.exe

Regards,
Vishal Shukla

Confidential communication
Westpac Banking Corporation (ABN 33 007 457 141)
Westpac Institutional Bank is a division of Westpac Banking 
Corporation

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


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

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

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

Re: [sqlite] SQLite Port/ODBC Driver Question

[Igor Korot]

Rob,

On Mon, Jul 10, 2017 at 7:06 AM, Rob Willett
 wrote:
> Vishal,
>
> SQLite isn't a traditional client/server relational database, therefore
> there isn't a port to open up. It runs on a local machine.

I believe SQLite can successfully be run remotely.

Thank you.

>
> Now there are wrappers around SQLite to extend it, I assume this ODBC driver
> is one of them.
>
> I suspect people here *may* know the answer regarding any ports the ODBC
> driver uses, but you may be better off asking the maintainer of the ODBC
> driver.
>
> Rob
>
>
> On 10 Jul 2017, at 1:31, Shukla, Vishal wrote:
>
>> Hi,
>> Am trying to open a firewall to the machine having sqlite database. Does
>> the SQLite database use a specific port number ? If not, then does the ODBC
>> connection to SQLite using ODBC driver use a port ?
>>
>> Any help will be greatly appreciated.
>>
>> SQLite ODBC Driver:
>> http://www.ch-werner.de/sqliteodbc/sqliteodbc.exe
>>
>> Regards,
>> Vishal Shukla
>>
>> Confidential communication
>> Westpac Banking Corporation (ABN 33 007 457 141)
>> Westpac Institutional Bank is a division of Westpac Banking Corporation
>> ___
>> sqlite-users mailing list
>> sqlite-users@mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite Port/ODBC Driver Question

[Rob Willett]

Vishal,

SQLite isn't a traditional client/server relational database, therefore 
there isn't a port to open up. It runs on a local machine.


Now there are wrappers around SQLite to extend it, I assume this ODBC 
driver is one of them.


I suspect people here *may* know the answer regarding any ports the ODBC 
driver uses, but you may be better off asking the maintainer of the ODBC 
driver.


Rob

On 10 Jul 2017, at 1:31, Shukla, Vishal wrote:


Hi,
Am trying to open a firewall to the machine having sqlite database. 
Does the SQLite database use a specific port number ? If not, then 
does the ODBC connection to SQLite using ODBC driver use a port ?


Any help will be greatly appreciated.

SQLite ODBC Driver:
http://www.ch-werner.de/sqliteodbc/sqliteodbc.exe

Regards,
Vishal Shukla

Confidential communication
Westpac Banking Corporation (ABN 33 007 457 141)
Westpac Institutional Bank is a division of Westpac Banking 
Corporation

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

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

[sqlite] SQLite Port/ODBC Driver Question

[Shukla, Vishal]

Hi,
Am trying to open a firewall to the machine having sqlite database. Does the 
SQLite database use a specific port number ? If not, then does the ODBC 
connection to SQLite using ODBC driver use a port ?

Any help will be greatly appreciated.

SQLite ODBC Driver:
http://www.ch-werner.de/sqliteodbc/sqliteodbc.exe

Regards,
Vishal Shukla

Confidential communication
Westpac Banking Corporation (ABN 33 007 457 141)
Westpac Institutional Bank is a division of Westpac Banking Corporation
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

[mohan_gn]

Thank you for the reply. 
I know it has been fixed. Since our product is already in field with older
version of SQLite, we want to know this bug's impact. We use simple queries
like 'select * from abc where col1=123 and col2=456'. We don't use any
JOINs, VIEWs, nested queries. The tables we use do have primary keys and
foreign keys. 
So I wanted to know whether in our cases the bug will impact and whether we
may be affected. 

Thank you,
Mohan




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Query-on-bug-fix-for-ticket-7ffd1ca1d2ad4ec-tp96175p96577.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

[Simon Slavin]

On 10 Jul 2017, at 7:15am, mohan_gn  wrote:

> Could anyone please answer above query? 

Do you mean this bug ?



If so, the bug was fixed in January.  Please download the latest version of 
SQLite and see whether you can reproduce the bug.

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

Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

[mohan_gn]

Hi All,

Could anyone please answer above query? 

Thank you very much,
Mohan



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Query-on-bug-fix-for-ticket-7ffd1ca1d2ad4ec-tp96175p96575.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users