John Ralls writes:
> On Aug 31, 2009, at 10:45 AM, Phil Longstaff wrote:
>
>> I've started to write a DBI backend test. Basically, it will create
>> a session with a set of data including (hopefully) all test cases.
>> It will then save that to a db, load it into another session, then
>> compare
Hmmm. I like it. I think it might work.
From: Josh Sled
To: Phil Longstaff
Cc: Gnucash Devel
Sent: Tuesday, September 1, 2009 9:26:54 AM
Subject: Re: DBI backend tests
Phil Longstaff writes:
> There's no problem doing this for sqlite3 (just
Phil Longstaff writes:
> There's no problem doing this for sqlite3 (just use /tmp/X). However,
> since there are differences for mysql and pgsql, I'd like to perform the test
> for all 3 databases. Any ideas on how "make check" could/should get urls for
> a mysql and pgsql database server
John Ralls writes:
> Yeah, don't. That is, don't actually talk to the real databases, just write
> a trivial pretend database (they're often called mocks) with the same
> function signatures and header names and so on so that you can build your
> test program with it instead of with pgsql or my
No problem with sqlite. Big problem with
mysql/postgresql. Now, embedded mysql might work... Hmmm..
Phil
From: John Ralls
To: Gnucash Devel
Sent: Monday, August 31, 2009 10:58:13 PM
Subject: Re: DBI backend tests
On Aug 31, 2009, at 10:45 AM, Phil
On Aug 31, 2009, at 10:45 AM, Phil Longstaff wrote:
I've started to write a DBI backend test. Basically, it will create
a session with a set of data including (hopefully) all test cases.
It will then save that to a db, load it into another session, then
compare the data in the two sessio
I've started to write a DBI backend test. Basically, it will create a session
with a set of data including (hopefully) all test cases. It will then save
that to a db, load it into another session, then compare the data in the two
sessions.
There's no problem doing this for sqlite3 (just use /
