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] 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
<rob.sql...@robertwillett.com> 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
<rob.sql...@robertwillett.com> 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

[sqlite] SqLite db ODBC

[Barry Trutor]

I am trying to locate an ODBC driver that I can use in the Windows Data
Link.

Is this doable? Does one exist?

Thanks, Barry

 

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

RE: [sqlite] SQLite and ODBC

[Steve O'Hara]

Hi,

I find I have to agree with the opinion that says keep the ODBC driver
should be external to the SQLite source.

Why? Well, how many other database engines, client/server or otherwise, come
with an ODBC driver embedded with the engine?  The answer of course is none.
Plenty of vendors supply drivers for all kinds of technologies - JDBC, OLEDB
etc but I'm not aware of a single one that embeds the driver with their
engine.

Surely the beauty of a loosely coupled system is the flexibility afforded to
the developer to choose the interface that best suits their needs, whilst
still maintaining a small, robust and fast backend.
The SQLite download pages are testimony to the enthusiasm of developers for
creating SQLite interfaces for a wide variety of
languages/environments/platforms.

I've used the SQLite ODBC driver in an environment whereby we use SQLite to
simulate differing client/server backends and I've found, by and large, that
despite the authors caveat about it being experimental, it works really
well.  Certainly better than the OpenLink driver to Informix which it
simulates!

Also, I'd rather Richard et al were concentrating their minds on the things
I CAN'T do, like improving the engine, rather than wasting their time
re-inventing the wheel on things I CAN do...

Steve


-Original Message-
From: Raymond Irving [mailto:[EMAIL PROTECTED]
Sent: 17 May 2004 21:08
To: [EMAIL PROTECTED]
Subject: RE: [sqlite] SQLite and ODBC



Hi,

I've download the version at http://www.ch-werner.de/sqliteodbc/ and it
works just fine. I was only making a suggestion that such a cool database
should come bundled with an ODBC driver (meaning it's part of the
development).

SQLite is very cool but it does not make any sense if it can't be (easily)
integrated with existing components. Rather than having the ODBC driver
separate I would suggest that it be a part of the teams plan for future
versions. Darren said that this would add more load the the developers but I
don't think it should really.

Making SQLite more connectable is something that the team should also
consider. Not everyone uses C or C++ and not all components have an
interface to bind an array. We just have to look at what tools we have
available and see how best we can make them integrate-able.

__
Raymond Irving



"Griggs, Donald" <[EMAIL PROTECTED]> wrote:
Regarding: "I was more think of ways to get an SQLite Database connected to
every day database objects and controls."

A good point!

This may be a naive comment of mine, but if you just forgot about the
vanilla sqlite download page, and instead considered page:
http://www.ch-werner.de/sqliteodbc/
to be THE release point for sqlite-cum-ODBC, would that not give you what
you need?


[writing for myself, and not on behalf of my company]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [sqlite] SQLite and ODBC

[Raymond Irving]

Hi,
 
I've download the version at http://www.ch-werner.de/sqliteodbc/ and it works just 
fine. I was only making a suggestion that such a cool database should come bundled 
with an ODBC driver (meaning it's part of the development).
 
SQLite is very cool but it does not make any sense if it can't be (easily) integrated 
with existing components. Rather than having the ODBC driver separate I would suggest 
that it be a part of the teams plan for future versions. Darren said that this would 
add more load the the developers but I don't think it should really. 
 
Making SQLite more connectable is something that the team should also consider. Not 
everyone uses C or C++ and not all components have an interface to bind an array. We 
just have to look at what tools we have available and see how best we can make them 
integrate-able.
 
__
Raymond Irving
 
 

"Griggs, Donald" <[EMAIL PROTECTED]> wrote:
Regarding: "I was more think of ways to get an SQLite Database connected to
every day database objects and controls."

A good point! 

This may be a naive comment of mine, but if you just forgot about the
vanilla sqlite download page, and instead considered page:
http://www.ch-werner.de/sqliteodbc/
to be THE release point for sqlite-cum-ODBC, would that not give you what
you need?


[writing for myself, and not on behalf of my company]

RE: [sqlite] SQLite and ODBC

[Griggs, Donald]

Regarding:  "I was more think of ways to get an SQLite Database connected to
every day database objects and controls."

A good point!   

This may be a naive comment of mine, but if you just forgot about the
vanilla sqlite download page, and instead considered page:
 http://www.ch-werner.de/sqliteodbc/
to be THE release point for sqlite-cum-ODBC, would that not give you what
you need?


[writing for myself, and not on behalf of my company]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [sqlite] SQLite and ODBC

[Darren Duncan]

At 12:29 PM -0700 5/17/04, Raymond Irving wrote:
Thanks for the feedback but I was not thinking about network 
connections to the database. I was more think of ways to get an 
SQLite Database connected to every day database objects and 
controls. Most of todays database tools use ODBC.

One typical example is how can I (easily) use SQLite inside VB for 
Databinding? If ODBC was standard then that would be a breeze not 
only for VB but for the hundreds for Rapid Application Development 
(RAD) software and components that are available today.
Regardless, one or more ODBC drivers are *already* available for 
SQLite, but are distributed separately.  Anyone who wants to use 
ODBC-dependant development tools with SQlite can download one of 
those drivers.  The fact that a driver isn't bundled with the SQlite 
core does not preclude its use with ODBC tools. -- Darren Duncan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [sqlite] SQLite and ODBC

[Mitchell Vincent]

Well put, Darren.
Raymond,
I would say that if you need ODBC then you need to use a different 
database (server) all together. SQLite fills the embedded database niche 
perfectly but it is not a replacement for MS-SQL, MySQl, PostgreSQl, 
Oracle or other database *servers*. If you need a RDBMS server you are 
better off using one instead of faking it with SQlite. PostgreSQL and 
MySQL both run on Windows and are free (well, PostgreSQL is free but who 
knows about MySQL these days.)

Best of luck!
Darren Duncan wrote:
At 7:25 AM -0700 5/17/04, Raymond Irving wrote:
I think SQLite should come standard with an odbc driver since ODBC is 
an "open standard"

I disagree.
Partly this is because D. Richard Hipp would then have to start 
certifying it like his own code and ensuring that it is always up to 
date with the core SQLite code, since they would get released together.  
That may be more responsibility than he wants.

Second, SQLite was intended first and foremost for embedding, and for 
the large fraction of people that use it that way, a database networking 
layer like ODBC is not going to be used anyway.  (That said, if SQLite 
was intended primarily for a client/server use, then I would more likely 
agree with you.)

The networking code would significantly increase the size of the core 
distribution, as well as make it harder to test, as networks have a lot 
more variables to be concerned with than a local disk-based system does.

By keeping the ODBC driver separate, those other people who see that as 
their specialty can focus on it on their own time table.  Let each 
person focus on what they do best, and all that.

Finally, while ODBC is very common, it isn't the only protocol for 
networking databases, and some people may prefer an alternative.

-- Darren Duncan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [sqlite] SQLite and ODBC

[Puneet Kishor]

Darren Duncan wrote:
At 7:25 AM -0700 5/17/04, Raymond Irving wrote:
I think SQLite should come standard with an odbc driver since ODBC is 
an "open standard"

I disagree.
..
Finally, while ODBC is very common, it isn't the only protocol for 
networking databases, and some people may prefer an alternative.


I agree with Darren. While ODBC would definitely make my life simpler, 
it probably better lies upon the SQLite community to create it as an 
add-on rather than have Richard include it in the core.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [sqlite] SQLite and ODBC

[Darren Duncan]

At 7:25 AM -0700 5/17/04, Raymond Irving wrote:
I think SQLite should come standard with an odbc driver since ODBC 
is an "open standard"
I disagree.
Partly this is because D. Richard Hipp would then have to start 
certifying it like his own code and ensuring that it is always up to 
date with the core SQLite code, since they would get released 
together.  That may be more responsibility than he wants.

Second, SQLite was intended first and foremost for embedding, and for 
the large fraction of people that use it that way, a database 
networking layer like ODBC is not going to be used anyway.  (That 
said, if SQLite was intended primarily for a client/server use, then 
I would more likely agree with you.)

The networking code would significantly increase the size of the core 
distribution, as well as make it harder to test, as networks have a 
lot more variables to be concerned with than a local disk-based 
system does.

By keeping the ODBC driver separate, those other people who see that 
as their specialty can focus on it on their own time table.  Let each 
person focus on what they do best, and all that.

Finally, while ODBC is very common, it isn't the only protocol for 
networking databases, and some people may prefer an alternative.

-- Darren Duncan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[sqlite] SQLite and ODBC

[Raymond Irving]

Hi,
 
I think SQLite should come standard with an odbc driver since ODBC is an "open 
standard"
 
__
Raymond Irving

RE: [sqlite] SQLite and ODBC/JDBC driver

[Clark, Chris]

> -Original Message-
> From: Jean-Eric Cuendet [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 06, 2004 6:06 AM
> To: [EMAIL PROTECTED]
> Subject: [sqlite] SQLite and ODBC/JDBC driver
> 


> There is an ODBC driver here: http://www.ch-werner.de/sqliteodbc/
> But there is no client/server, the server is embedded in the 
> ODBC driver 
> on the client.
> 
> I think that we could modify the ODBC driver to communicate through 
> sockets with the SQLite on the server but that would be a lot 
> of work..

Sounds like you want an ODBC proxy server. I've not used one but there are some 
floating around, just "google" for odbc proxy. This one looks interesting 
http://www.fastflow.it/dbtcp/


SQLRelay can do a similar job (and can connect to ODBC) BUT it does not have an ODBC 
client api, it has it's own.

Chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]