GnuCash is totally a volunteer project. Everyone here only is around
because they consider this work interesting in one way or another.
Nobody got paid to do this -- and in particular, you paid nothing to
anybody for obtaining gnucash, so "requesting features" should be done
with some appropriate politeness. Stating that you are "not interested
in signing up for the mailing list" doesn't quite fall in the category
of politeness. Or, spoken the other way round, it may happen that we
are "not interested in reading yet another bug report" if it already
starts with such a statement. Having said that, now for the questions:

I don't understand your number one. Do you mean you are asking for the
ability to email an invoice, and to do this either as a HTML email or
as a PDF email? That's what I would guess, but you should clear up
your request here or else nobody understands it anyway. Starting an
email directly out of gnucash is an interesting idea, but it would
need greater discussion on how to actually do this (e.g. which email
address book is used etc). Discussions like these happen on the
gnucash-devel mailing list. If you want to see this feature become
reality there's simply no way around the mailing list.

What do you mean by number two? THe current data store can either be
one single disk file or a PostgreSQL database. Are you asking to have
MySQL as another possibility for the data store? Then we have to
disappoint you -- there have been giantic discussions on gnucash-devel
about which database should be supported and which shouldn't. The
conclusion was that PostgreSQL is used for now, some generic
abstraction layer should be used in the future, but MySQL in
particular won't be an option as long as several database features are
still missing in there.

I apologize. I was having a bad day.  I also get over 200 email messages per day 
from various email lists.  Who has time?  It get very frustrated in that everybody 
and his brother always asks for the same information every time I sign up for one.  
I'm on several lists (mysql, procmail, dbmail, powerdns, nanog, majordomo, etc.) It 
seems to be the only way to get support for anything and its very cool.  Most folks 
on the lists are helpful.  Its just a pain in the backside to set up the subscription 
and filters.  Its almost as annoying as trying to find a bug in bugzilla.   
 
Gnu-cash has some features that are very nice and better than the competition 
IMHO.   
 
I did notice that as I was entering data for a new customer, one of the fields in the 
customer entry field is for an email address.  My thought is that you use that email 
address.  When I say as HTML, the layout of the invoice could be done as an 
HTML attachment or even an html email.  As a PDF, one would have to pass it 
through a PDF filter, mime encode it, then attach it to an email.  Currently, 
GnuCash does allow me to print through a PDF filter.  I figure its just another 
couple of steps to print it to a temporary file and email it. 
 
Couple the ability to send an invoice via email with the scheduled tasks and one 
could have automatic invoicing of customers and those invoices could be sent by 
email.  It would be a very nice feature. 
 
The same would also go for statements. 
 
On Number 2. 
what is it that MySQL is missing that prevents it from being used as a data store?  
Given the native XML file format (not sure how scaleable that is, but I'm not a C 
programmer and don't know about advanced search algorithms.)  PostGreSQL just 
doesn't scale the way MySQL does.  It scales to large files even better than 
Oracle.  I would hope that the XML backend scales better than Intuit's files.  Intuit 
begins to slow way down once it gets beyond a couple of G'Bytes.  DB Servers 
are just much better at processing the files.  Some are better than others. 
 
Thanks, I might sign up for the email lists, but when I tried to look at the archives 
last night, I kept getting asked for a password and couldn't access anything at all. 
 
Thanks for your time. 
 
 

Hi.

First, I changed the Severity to enhancement and changed the Summary
to more accurately reflect the actual requests.  Honestly, this should
have been two requests because they are not related, but that's a
different issue.  :)


1) The customer information is gathered on the premise that we might
use it later.  Yes, there is an email entry.  No, it is not used. 
Yes, it would be "nice" if it could be used.

2) The main reason MySQL can't be used is that it doesn't have two
features required by the current implementation: stored procedures and
notifications.

Having said that, we ARE working on a libdbi re-write, which should
give you MySQL support (we're planning to use it for SQLite support
and get rid of XML as a data storage format and use it only for
import/export).

I hope this helps.

PS: I am reopening this bug because I understand what it's asking for.

*** Bug 149735 has been marked as a duplicate of this bug. ***

Emailing invoices falls under my area.

Since we now have a libdbi rewrite targetting 2.4, I suggest we drop that part of this and leave it as "RFE: E-mail invoices".  BTW, this should have been split into 2 RFEs.

Completely new feature request which the current gnucash developers consider
completely outside of the current gnucash scope. Please record such plans
somewhere else, but not in bugzilla. Thanks.

GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=125281. Please update any external references or bookmarks.