On Sat, Jan 09, 2010 at 11:06:48AM +0100, David Paleino wrote:
> > I hope you will carefully and critically review the project.
>
> Before, I need to start it -- here it just segfaults ;)
:-(
> Well, I don't, but I'd like to see more choices for the user. Possibly, if
> the
> dental practice only has one computer, installing MySQL/PostgreSQL is
> overkill, and SQLite could be a better choice.
I strongly disagree. SQLite is just no option for practice management because
this is just not light.
> For Client-Server solutions,
> I'd like to see both MySQL and PostgreSQL implemented -- maybe using a
> backend-agnostic module.
I do not see any real sense into this. If you try to be
backend-agnostic you are limiting the features of the database to a
small common set of features rather than making profit from the feature
richness of PostgreSQL. I will not start a private Database flamewar
with you because there are way to much in the internet. There are
perfect use cases for MySQL - IMHO practice management is not such
a case and you need some more features. Writing a practice management
system is not about picking any tool I know by chance but rather find
out which is really capable for the task.
> > If you have contact to upstream
>
> I already sent him a mail, to improve the provided tarball a bit, before even
> starting the packaging work.
Great.
> > I would strongly recommend building a connection to GNUmed which has a quite
> > developed database model which enables I18N etc.
>
> Connection of what type, and in what ways? :)
1. Communication with the authors
2. Read and understand the database model
> Thanks for writing me -- I would've committed this to debian-med nevertheless
> ;)
Ahh, right - I intended to actually CC Debian Med - so I do now and
hope even if I deleted some quotes it is understandable anyway.
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
