Re: QOF-to-SQL Proof of Concept

2004-06-06 Thread Derek Atkins
[EMAIL PROTECTED] (Linas Vepstas) writes: > ? There are currently four back-ends, two operational and two in > disrepair. The ones that work are xml and sql, the rpc and the http > backends are not used and no longer work. As far as I know, the front > end doesn't suffer from limitations in the

Re: QOF-to-SQL Proof of Concept

2004-06-06 Thread Linas Vepstas
Hi John, On Sat, May 29, 2004 at 11:26:09PM -0700, John Arrowwood was heard to remark: > You've got to be careful here. Some things to ponder: > > In a multi-user environment, you don't want user A to be blocked because > user B is trying to do something. If they are blocked, it should be for

Re: QOF-to-SQL Proof of Concept

2004-06-04 Thread John Arrowwood
now. But on the off chance that you hadn't, I figured I'd toss it out there! :) From: Derek Atkins <[EMAIL PROTECTED]> To: Benjamin Carlyle <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: QOF-to-SQL Proof of Concept Date: Sat, 29 May 2004 22:59:53 -0400 Benjamin Carlyle

Re: QOF-to-SQL Proof of Concept

2004-06-02 Thread Derek Atkins
[EMAIL PROTECTED] (Linas Vepstas) writes: > mysql should 'just work' under the odbc or the libdbi interfaces. > I have not even attempted sqllite; i'm less clear if that would work > with either. Since odbc basically sucks rocks, I wouldn't mind having a > 'native' sqllite driver. sqlite should

Re: QOF-to-SQL Proof of Concept

2004-06-02 Thread Linas Vepstas
On Wed, Jun 02, 2004 at 12:27:47AM -0400, Derek Atkins was heard to remark: > James Richardson <[EMAIL PROTECTED]> writes: > > >> Don't gocrazy hjust yet, wait for the prototype to get finished. > >> There's still a lot of work left. > > > > I would like to help, especially with the mysql (non e

Re: QOF-to-SQL Proof of Concept

2004-06-01 Thread Derek Atkins
James Richardson <[EMAIL PROTECTED]> writes: >> Don't gocrazy hjust yet, wait for the prototype to get finished. >> There's still a lot of work left. > > I would like to help, especially with the mysql (non existent?) stuff. > Anyway, I will pull the cvs code from sf.net and take a look. MySQL

Re: QOF-to-SQL Proof of Concept

2004-06-01 Thread James Richardson
On Wed, May 26, 2004 at 09:07:53AM -0500, Linas Vepstas wrote: > On Mon, May 24, 2004 at 11:10:49AM -0400, Derek Atkins was heard to remark: > > [EMAIL PROTECTED] (Linas Vepstas) writes: > > > > > FYI, > > > > > > I just finished coding a proof-of-concept for saving & restoring > > > arbitrary QOF

Re: QOF-to-SQL Proof of Concept

2004-05-30 Thread Derek Atkins
d in order to make it work. > > Or, pick one database and say "this is it, folks! it works here, no > where else." But we both know that there is a reason you don't want > to do that... > > Now, you may have already planned on doing all of that. Don't know. >

Re: QOF-to-SQL Proof of Concept

2004-05-29 Thread Linas Vepstas
On Sat, May 29, 2004 at 11:25:31PM -0400, Derek Atkins was heard to remark: > > Ok, so this construct DOES work.. The "BEGIN TRANSACTION" is > effectively the "LOCK". :) In the new work, I'm planning on making the locking be database-dependent, so even non-locking db's could be suported in at

Re: QOF-to-SQL Proof of Concept

2004-05-29 Thread Benjamin Carlyle
On Sun, 2004-05-30 at 12:59, Derek Atkins wrote: > Benjamin Carlyle <[EMAIL PROTECTED]> writes: > > Whenever you say "BEGIN TRANSACTION;" a exclusive lock will be placed on > > the whole database. When you commit or rollback your transaction the > > lock is removed. Any insert, update, or other ope

Re: QOF-to-SQL Proof of Concept

2004-05-29 Thread Derek Atkins
Benjamin Carlyle <[EMAIL PROTECTED]> writes: >> I'm not sure a BEGIN TRANSACTION / COMMIT TRANSACTION is sufficient to >> do this, unless we can actually perform a SELECT and get back real >> data in the middle of a transaction? > > # Calculate update ahead of time, allowing user to > # enter new

Re: QOF-to-SQL Proof of Concept

2004-05-29 Thread Derek Atkins
Benjamin Carlyle <[EMAIL PROTECTED]> writes: > The database handles it for you. > > Whenever you say "BEGIN TRANSACTION;" a exclusive lock will be placed on > the whole database. When you commit or rollback your transaction the > lock is removed. Any insert, update, or other operation that modifie

Re: QOF-to-SQL Proof of Concept

2004-05-29 Thread Benjamin Carlyle
On Sun, 2004-05-30 at 00:30, Derek Atkins wrote: > I'm envisioning multiple gnucash applications "opening" the same > database and then each app reading/writing as necessary for its > operation. Obviously the writes need to be serialized (you can't have > both apps "writing" at the same time, but

Re: QOF-to-SQL Proof of Concept

2004-05-29 Thread Derek Atkins
Benjamin Carlyle <[EMAIL PROTECTED]> writes: > On Thu, 2004-05-27 at 00:14, Derek Atkins wrote: >> [EMAIL PROTECTED] (Linas Vepstas) writes: >> > but SQLLite is single-user, right? No multi-user support. >> No, there is multi-user support in SQLite (at least according to their >> website). It lo

Re: QOF-to-SQL Proof of Concept

2004-05-28 Thread Benjamin Carlyle
On Thu, 2004-05-27 at 00:14, Derek Atkins wrote: > [EMAIL PROTECTED] (Linas Vepstas) writes: > > but SQLLite is single-user, right? No multi-user support. > No, there is multi-user support in SQLite (at least according to their > website). It lock()'s the database file for writes. I think I've b

Re: QOF-to-SQL Proof of Concept

2004-05-26 Thread Derek Atkins
[EMAIL PROTECTED] (Linas Vepstas) writes: >> latter, because some SQL engines that I'd like to use don't support >> notify events (e.g. SQLite). > > but SQLLite is single-user, right? No multi-user support. No, there is multi-user support in SQLite (at least according to their website). It lock

Re: QOF-to-SQL Proof of Concept

2004-05-26 Thread Linas Vepstas
On Mon, May 24, 2004 at 11:10:49AM -0400, Derek Atkins was heard to remark: > [EMAIL PROTECTED] (Linas Vepstas) writes: > > > FYI, > > > > I just finished coding a proof-of-concept for saving & restoring > > arbitrary QOF objects to SQL tables & back. I've now started on > > a prototype that will

Re: QOF-to-SQL Proof of Concept

2004-05-24 Thread Derek Atkins
Agreed, I guess I didn't make that clear in my initial mail. -derek Eneko Lacunza <[EMAIL PROTECTED]> writes: > Hi, > > I think it should be optional to store the user/password for database > access, for maximun privacy; like with the web navigator and login > forms. If not stored (gconf o

Re: QOF-to-SQL Proof of Concept

2004-05-24 Thread Eneko Lacunza
Hi, I think it should be optional to store the user/password for database access, for maximun privacy; like with the web navigator and login forms. If not stored (gconf or whatever), Gnucash should ask for it every time user opens the book. My 0.01 eurocent ;) P.D.: Keep on your excelent

Re: QOF-to-SQL Proof of Concept

2004-05-24 Thread Derek Atkins
[EMAIL PROTECTED] (Linas Vepstas) writes: > FYI, > > I just finished coding a proof-of-concept for saving & restoring > arbitrary QOF objects to SQL tables & back. I've now started on > a prototype that will 'do it correctly' i.e. mutate into the final > version. You probbly don't want to look a

QOF-to-SQL Proof of Concept

2004-05-24 Thread Linas Vepstas
FYI, I just finished coding a proof-of-concept for saving & restoring arbitrary QOF objects to SQL tables & back. I've now started on a prototype that will 'do it correctly' i.e. mutate into the final version. You probbly don't want to look at the code, since its 'all wrong', but its in the dw