Quoting Phil Longstaff <[EMAIL PROTECTED]>:
> Derek Atkins wrote:
> to switch.
Do you want to do this in the gda-dev or would you like a new branch
to work from? Branches are cheap.
>>> At this point, I'll work in gda-dev.
>>
>> Okay. I was just thinking that maybe "dbi-dev" would
Derek Atkins wrote:
to switch.
>>> Do you want to do this in the gda-dev or would you like a new branch
>>> to work from? Branches are cheap.
>> At this point, I'll work in gda-dev.
>
> Okay. I was just thinking that maybe "dbi-dev" would be a more
> appropriate name. But up to you.
What
Phil Longstaff <[EMAIL PROTECTED]> writes:
> Derek Atkins wrote:
>> Phil Longstaff <[EMAIL PROTECTED]> writes:
>>
>> My appologies for sounding like a broken record, but if you look at
>> MythTV they show how to support both MySQL and PG in an automated
>> fashion. At least I'm pretty sure they
Derek Atkins wrote:
> Phil Longstaff <[EMAIL PROTECTED]> writes:
>
> My appologies for sounding like a broken record, but if you look at
> MythTV they show how to support both MySQL and PG in an automated
> fashion. At least I'm pretty sure they can create and update tables
> for both DBs.
I'll
"Nathan Buchanan" <[EMAIL PROTECTED]> writes:
>> The assumption here (in both #1 and #2) is that GDA-4 will be
>> released sooner than that gda-dev branch will finish. I have seen
>> no such assurance. What happens if gda-branch finishes, gets
>> merged back into trunk, but GDA-4 hasn't been rel
Phil Longstaff <[EMAIL PROTECTED]> writes:
> My memory is that I chose GDA over DBI because DBI did not seem to be
> maintained. In fact, there is nothing on their page re release between
> Nov 2005 and Feb 2007 (I remember starting the project in 2006). What
> we are now finding is that GDA-3 w
"Albert Lash" <[EMAIL PROTECTED]> writes:
>>>
>>> One problem with libdbi is that its scope doesn't cover everything that
>>> libgda's does. From what I can tell, libdbi doesn't have any apis to
>>> cover table/index creation, and that is one area that has a lot of
>>> individuality (e.g. autoinc
Phil Longstaff <[EMAIL PROTECTED]> writes:
> Derek Atkins wrote:
>> Phil Longstaff <[EMAIL PROTECTED]> writes:
>>
Or would it be more expedient to pick a technology that has a proven
track record, proven stability, is NOT a moving target, and is
already available in most distributi
Hi,
On Tue, Jun 3, 2008 at 8:19 AM, Derek Atkins <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Sorry for the delay, but I've been busy offline most of the
> weekend and yesterday so I've let this thread sit for a bit.
> More comments inline.
>
> "Nathan Buchanan" <[EMAIL PROTECTED]> writes:
>
> > So...In t
Derek Atkins wrote:
>> 2. Use GDA V4. We will probably send time fixing bugs here, but we are almost
>> guaranteed that a release will happen. The advantages of this approach is
>> that
>> we will be current with the new GDA and releases will be done for us (or in
>> conjunction with us - dependin
>>
>> One problem with libdbi is that its scope doesn't cover everything that
>> libgda's does. From what I can tell, libdbi doesn't have any apis to
>> cover table/index creation, and that is one area that has a lot of
>> individuality (e.g. autoinc integer fields).
>
> Is that the only individua
Derek Atkins wrote:
> Phil Longstaff <[EMAIL PROTECTED]> writes:
>
>>> Or would it be more expedient to pick a technology that has a proven
>>> track record, proven stability, is NOT a moving target, and is
>>> already available in most distributions?
>> One problem with libdbi is that its scope d
Phil Longstaff <[EMAIL PROTECTED]> writes:
>> Or would it be more expedient to pick a technology that has a proven
>> track record, proven stability, is NOT a moving target, and is
>> already available in most distributions?
>
> One problem with libdbi is that its scope doesn't cover everything th
Hi,
Sorry for the delay, but I've been busy offline most of the
weekend and yesterday so I've let this thread sit for a bit.
More comments inline.
"Nathan Buchanan" <[EMAIL PROTECTED]> writes:
> So...In the end, what's our options?
>
> 1. Use GDA V3. We will spend time fixing bugs in V3 that wil
Quoting Graham Leggett <[EMAIL PROTECTED]>:
>> In your case you're talking about a completely different paradigm.
>> You're talking POS/Orders, and the gnucash business features don't
>> implement that right now. For that you should probably just forego
>> the business features because you're nev
Derek Atkins wrote:
Eh? I receive a bill from my vendor. It's not due for another
20 days. I enter it into gnucash and then later on pay it.
Some vendors are COD only, which means the payment will almost always
come before the invoice. Or the payment is captured before the bill is
captur
[[ Shoot! I keep forgetting to reply to list... Sorry Derek for all the
doubles I cause in your mailbox ]]
Note: I have changed the subject to separate this topic from the GDA one.
On Sunday 1 June 2008, you wrote:
> > On top of this, you may have captured the bills in a different order
> > to t
hi,
Quoting Graham Leggett <[EMAIL PROTECTED]>:
> Derek Atkins wrote:
>
>> gncInvoice.c
>>
>> in particular the code that implements the invoice and payment processing
>> and the balancing code to make sure payment are split across invoices
>> properly.
>
> I have found that the current implement
Derek Atkins wrote:
gncInvoice.c
in particular the code that implements the invoice and payment processing
and the balancing code to make sure payment are split across invoices
properly.
I have found that the current implementation of this particular
functionality doesn't work that well, as
Nathan Buchanan wrote:
2. Use GDA V4. We will probably send time fixing bugs here, but we are
almost guaranteed that a release will happen. The advantages of this
approach is that we will be current with the new GDA and releases will be
done for us (or in conjunction with us - depending on how c
So...In the end, what's our options?
1. Use GDA V3. We will spend time fixing bugs in V3 that will probably not
be released in a bugfix release of GDA. The advantages of this approach are
that we get access to sqlite, mysql, and postgres. The disadvantage is that
we will probably have to ship our
2008/5/31 Daniel Espinosa <[EMAIL PROTECTED]>:
> 2008/5/30 Derek Atkins <[EMAIL PROTECTED]>:
>> "Daniel Espinosa" <[EMAIL PROTECTED]> writes:
>>
>>> I just want to point that if you use V4 you may will get inmediatly
>>> access to SQLite database, and after the API is stable enough the
>>> other da
2008/5/30 Derek Atkins <[EMAIL PROTECTED]>:
> "Daniel Espinosa" <[EMAIL PROTECTED]> writes:
>
>> I just want to point that if you use V4 you may will get inmediatly
>> access to SQLite database, and after the API is stable enough the
>> other database providers will be on the road.
>
> How long in
2008/5/30 Derek Atkins <[EMAIL PROTECTED]>:
> Daniel,
>
> My major concern here is that a year ago you were rallying for
> GDA and GdaQuery. Phil threw out a bunch of his work to target
> GDA-3 with GdaQuery. Now here we are, 6 or 9 months later, and
> the GDA team has moved on to GDA-4 already a
Derek Atkins wrote:
> Daniel,
>
> My major concern here is that a year ago you were rallying for
> GDA and GdaQuery. Phil threw out a bunch of his work to target
> GDA-3 with GdaQuery. Now here we are, 6 or 9 months later, and
> the GDA team has moved on to GDA-4 already and are dropping GdaQuer
Quoting Graham Leggett <[EMAIL PROTECTED]>:
> Derek Atkins wrote:
>
>> Unfortunately it's not that easy. That check is in there because the
>> underlying code uses the Value + AccountType to determine if this is an
>> "Invoice" or a "Payment". All the linkage logic is based on the invariant
>> t
Derek Atkins wrote:
Unfortunately it's not that easy. That check is in there because the
underlying code uses the Value + AccountType to determine if this is an
"Invoice" or a "Payment". All the linkage logic is based on the invariant
that an Invoice is "positive" and a Payment is "negative"
Getting back to the gda stuff, the key question seems to be: Can support for
mysql and postgresql wait?
If so, then V4 seems like a good choice to me, since Phil has said (I think)
that it works well enough with sqlite for our purposes. Support for the
other databases can be added as V4 evolves.
[[Sorry, forgot to reply to list]]
I have created a feature request for credit notes in bugzilla:
http://bugzilla.gnome.org/show_bug.cgi?id=535781
I have added most of the parts of this thread I considered relevant, together
with some freewheeling on the implementation.
Although I'll probably n
Quoting Graham Leggett <[EMAIL PROTECTED]>:
> Derek Atkins wrote:
>
>> A Process Payment gives you that "Negative" number. What you would
>> do is Process Payment to, say, your checking account. Then after
>> the transaction gets posted you can go in and change it from Checking
>> to Income. Ma
Derek Atkins wrote:
A Process Payment gives you that "Negative" number. What you would
do is Process Payment to, say, your checking account. Then after
the transaction gets posted you can go in and change it from Checking
to Income. Make sure you only change the account, not the AMOUNT.
Chang
"Daniel Espinosa" <[EMAIL PROTECTED]> writes:
> I just want to point that if you use V4 you may will get inmediatly
> access to SQLite database, and after the API is stable enough the
> other database providers will be on the road.
How long in the future is this "down the road"? I'm concerned
ab
Daniel,
My major concern here is that a year ago you were rallying for
GDA and GdaQuery. Phil threw out a bunch of his work to target
GDA-3 with GdaQuery. Now here we are, 6 or 9 months later, and
the GDA team has moved on to GDA-4 already and are dropping GdaQuery,
the very interface you were s
Geert Janssens <[EMAIL PROTECTED]> writes:
> On Wednesday 28 May 2008, Derek Atkins wrote:
>> Geert Janssens <[EMAIL PROTECTED]> writes:
>> > On Tuesday 27 May 2008, you wrote:
>> >> Gnucash has some bizaare flaws though: gnucash will actively stop you
>> >> trying to give your customer a refund b
I've read all your other comments and is the same as before I "try" to
re-write most of the GC's core, you don't want to lesen the others,
the I don't plan to work on GC's as actualy is. If I can help Phil
improving GDA it's Ok. If some others work to modify the GC's core to
create a bussiness libr
2008/5/26 Phil Longstaff <[EMAIL PROTECTED]>:
> Graham Leggett wrote:
>> Phil Longstaff wrote:
>>
>>> Well, V4 basically works with the sqlite provider. There were a number
>>> of memory leaks and other small issues. However, there are a number of
>>> problems with the V4 mysql provider - it's no
On Wednesday 28 May 2008, Derek Atkins wrote:
> Geert Janssens <[EMAIL PROTECTED]> writes:
> > On Tuesday 27 May 2008, you wrote:
> >> Gnucash has some bizaare flaws though: gnucash will actively stop you
> >> trying to give your customer a refund by refusing to post an invoice
> >> with a negative
Hi,
On Donnerstag, 29. Mai 2008, Josh Sled wrote:
[...]
> Derek, I'm not sure what you hope to accomplish by laughing at people who
> want to make the app better, and advocate for users, but it's really
> off-putting.
[...]
Hmm, that comes from the guy who slammed me when I was merely asking abou
Derek Atkins <[EMAIL PROTECTED]> writes:
> Previous, Graham said:
>
>>> Users needs win I am afraid, if necessary I'll patch gnucash to do it
>>> myself.
>
> Hahahahahahaha!! Wow, now you're REAY funny! Have you
> forgotten that GnuCash is a Volunteer effort? *laughs* "Users"?
> While
Derek Atkins wrote:
Hahahahahahaha!! Wow, now you're REAY funny! Have you
forgotten that GnuCash is a Volunteer effort? *laughs* "Users"?
Come across to Apache sometime. We take our users seriously over there.
Last I checked Apache had a whole big funded foundation backing their
Graham Leggett <[EMAIL PROTECTED]> writes:
> Derek Atkins wrote:
>
>> Hahahahahahaha!! Wow, now you're REAY funny! Have you
>> forgotten that GnuCash is a Volunteer effort? *laughs* "Users"?
>
> Come across to Apache sometime. We take our users seriously over there.
Last I checked Ap
Derek Atkins wrote:
Hahahahahahaha!! Wow, now you're REAY funny! Have you
forgotten that GnuCash is a Volunteer effort? *laughs* "Users"?
Come across to Apache sometime. We take our users seriously over there.
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Signa
Geert Janssens <[EMAIL PROTECTED]> writes:
> [[Sorry, this was meant to go on the list as well]]
>
> On Tuesday 27 May 2008, you wrote:
>> Gnucash has some bizaare flaws though: gnucash will actively stop you
>> trying to give your customer a refund by refusing to post an invoice
>> with a negativ
Am Dienstag, 27. Mai 2008 18:05 schrieb Graham Leggett:
> Derek Atkins wrote:
> > Nope. Not a bug. It's a design decision. It has nothing to do
> > with DB "transactions".. Instead it's a question of DB coherency.
> >
> > Basically, it's not supported for a user to modify GnuCash's data
> > sto
[[Sorry, this was meant to go on the list as well]]
On Tuesday 27 May 2008, you wrote:
> Gnucash has some bizaare flaws though: gnucash will actively stop you
> trying to give your customer a refund by refusing to post an invoice
> with a negative total. In the mean time we hack the XML by hand (!
Geert Janssens wrote:
And I have been looking around, although I didn't migrate yet because of the
huge effort it usually takes: there's
* Compiere: it does ERP (enterprise resource planning), BPM (Business Project
Management) and accounting. It's maintained by a company also called
Compiere,
On Tuesday 27 May 2008, Graham Leggett wrote:
> Derek Atkins wrote:
> > It sounds like you really want GnuE. I suggest you look there.
>
> "ZoneEdit DNS services for this domain have expired."
>
> Looks like it is a dead project to me.
>
That's the comment I read in google, but for me the link
(h
I've spent the past few weeks trying to port to libgda V4. On the
libgda mailing list, I was told that a bug I reported against V3 would
not be fixed because effort was going into V4. I also wanted to work
with V4 to help find any problems as soon as possible.
Well, V4 basically works with the s
I hit a number of roadblocks.
1) My development machine died
2) After I replaced it, I got myself locked out of gnucash subversion
3) I "upgraded" to libgda 2.99.5 which introduced a show-stopper bug.
I'm now back to 2.99.3 (2.99.4 was very short-lived) and will be able to
continue work.
Phil
_
49 matches
Mail list logo
