On 17 Sep 2008, at 20:48, Ted Thibodeau Jr. wrote:
I understood the local cache to be a learning and/or small version
of what would then be done with a remote engine, which would not
be SQLite.
Yes, that is correct. Some of the database transaction will need to be
on the client side.
It won
Devon wrote:
> He was talking about using a local sqlite cache so at least in my
> view I don't see the point in using ODBC for that. SQLite really
> doesn't have too much different from generic SQL that would make
> it hard to learn especially since there are some nice wrapper
> classes around it
dreamcat7 wrote:
> As a developer I aswell am finding it hard to evaluate these
> options myself and without prior experience. For example I
> would be drawn to the prospect of learning the same api for
> both the local and remote database. (typically id like to
> cache the data downloaded from the
He was talking about using a local sqlite cache so at least in my view I
don't see the point in using ODBC for that. SQLite really doesn't have
too much different from generic SQL that would make it hard to learn
especially since there are some nice wrapper classes around it already.
Devon
T
Precisely my point: how do you go about evaluating which of these is
the better option ?
I hoped i was clear enough in my previous mail.
On 17 Sep 2008, at 20:06, Ted Thibodeau Jr. wrote:
Devon wrote:
OS X has libsqlite3 built in. You just have to include the header
file and link to the li
On Sep 17, 2008, at 11:42 AM, dreamcat7 wrote:
I would be drawn to
the prospect of learning the same api for both the local and remote
database. (typically id like to cache the data downloaded from the
data onto a local sqlite DB). I did find only one ODBC driver for
sqlite
http://www.ch-we
Devon wrote:
> OS X has libsqlite3 built in. You just have to include the header
> file and link to the library. It's C based and you can write an
> Objective-C wrapper functions around it. There are already some
> good ones like FMDatabase or Quicklite.
Well, yes ... but it's not an ODBC driver
OS X has libsqlite3 built in. You just have to include the header file
and link to the library. It's C based and you can write an Objective-C
wrapper functions around it. There are already some good ones like
FMDatabase or Quicklite.
Devon
dreamcat7 wrote:
Hi,
As a developer I aswell am f
Hi,
As a developer I aswell am finding it hard to evaluate these options
myself and without prior experience. For example I would be drawn to
the prospect of learning the same api for both the local and remote
database. (typically id like to cache the data downloaded from the
data onto a l
> Can anyone suggest a multi Database library for use in developing a
> Cocoa based app? At least support for Oracle, MySQL and PostgreSQL
> would be required.
>
> I notice that Python has good database support. Would developing a
> PyObjC app be a better way to go?
ODBC... If you're working with
Can anyone suggest a multi Database library for use in developing a Cocoa
based app? At least support for Oracle, MySQL and PostgreSQL would be
required.
I notice that Python has good database support. Would developing a PyObjC
app be a better way to go?
thanks,
Andrew
11 matches
Mail list logo
