Hi.
Well, of course, the RDBMS (here MySQL) is handling table locking (not
only with BDB tables).
But, because this seems rather obvious to me, maybe I misunderstood
your question?
Bye,
Benjamin.
On Thu, Feb 08, 2001 at 02:54:47PM -0800, [EMAIL PROTECTED] wrote:
> Hi,
>
> One thing I
OBDC's strength is that it is almost universal in accessing files, not
speed, and that may be the reason why using the jet engine will produce
quicker results. I don't know if it will work on your end, but I moved from
using MyOdbc to the following statement in accessing mysql database:
strCon
Hi,
One thing I have always wondered, how do you deal with table locking if you
have a number of people using mySQL with ODBC?
Does ODBC handle it? Does Access do it? Can mySQL do it with Berkeley?
I am esp talking if you are using mySQL from many different locations and
working on the same tab
Re your second query - without looking at the docs,
unix_timestamp(field1) - unix_timestamp(field2) would give you the
difference in seconds - I;m sure there's a cleaner way though!
On Thu, 8
Feb 2001, Quickling wrote:
> Hi,
>
> Question 1:
> ---
> We've got a server app that does a
Actually there is no reason to expect MySQL to perform better than
Access for a nominally sized database and everything running on one PC.
Access was designed and optimized for JET whereas ODBC is a
general-purpose API.
Also, the connection method impacts this significantly, as do the
complexity
On Thu, 8 Feb 2001, Quickling wrote:
> Date: Thu, 08 Feb 2001 17:02:59 -0500
> From: Quickling <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: MySQL vs Access; you'd *think* the choice is obvious...
>
> Hi,
>
> Question 2:
> ---
> Is
Quickling wrote:
>
> Hi,
>
> Question 1:
> ---
> We've got a server app that does a lot of 'small' database reads and
> writes. We were originally using MS Access via DAO (Jet Engine) and we
> wanted to tighten up DB performance, so we've written a general ODBC
> database wrapper
Hi,
Question 1:
---
We've got a server app that does a lot of 'small' database reads and
writes. We were originally using MS Access via DAO (Jet Engine) and we
wanted to tighten up DB performance, so we've written a general ODBC
database wrapper object, but mainly just to connect
