I need to choose a good combination of front & back ends for a database application.
The application is quite simple. It is basically a muster, where employees can sign in by entering an employee-ID.
For this I need to store a database of all employees with some basic fields like ID, name, etc. When someone enters an ID, a validity check is done and if valid the ID is stored into a table.
My requirements:
1. Application will need to work on throw-away machines, like a 286 or 386. But the machine will be used solely for this application.
2. I need to use a language which is easy to learn (time constraint), given the fact that I only have knowledge of C and some C++.
3. Tomorrow I may need to add some more functionalities to the application. Basically running different queries for retrieving data. Also size of the employee database may increase. For starters I am looking at 100 to 1000 employees.
For the database I guess mySQL would be ideal. (or is there a better option?) What should I use for the front end? And reasons for it.
Many thanks, Nikhil.
____________________________________________________ Buy Feng Shui Package for Rs. 151/- only, at http://shopping.rediff.com/shopping/fengshui_mailer.htm
On 4 Jul 2001, Nikhil Karkera wrote:
For the database I guess mySQL would be ideal. (or is there a better
postgresql would be better in that it has better performance with concurrent connections.
option?) What should I use for the front end? And reasons for it.
python would be a good idea. easy to learn (should take a day or two, less if you learn while coding), has all necessary database drivers, and would be easy to extend the application through classes.
Philip
considering you want this application (as well as database?) to run off a 286 as well you could look at using this application with a flat file database as well :-) the fox's were a good idea once upon a time but that would take some learning.
Rahil ----- Original Message ----- From: "Nikhil Karkera" ianmalc@rediffmail.com To: linuxers@mm.ilug-bom.org.in Sent: Wednesday, July 04, 2001 3:26 PM Subject: [ILUG-BOM] Best tools for a database application?
I need to choose a good combination of front & back ends for a database application.
The application is quite simple. It is basically a muster, where employees can sign in by entering an employee-ID.
For this I need to store a database of all employees with some basic fields like ID, name, etc. When someone enters an ID, a validity check is done and if valid the ID is stored into a table.
My requirements:
- Application will need to work on
throw-away machines, like a 286 or 386. But the machine will be used solely for this application.
- I need to use a language which is easy
to learn (time constraint), given the fact that I only have knowledge of C and some C++.
- Tomorrow I may need to add some more
functionalities to the application. Basically running different queries for retrieving data. Also size of the employee database may increase. For starters I am looking at 100 to 1000 employees.
For the database I guess mySQL would be ideal. (or is there a better option?) What should I use for the front end? And reasons for it.
Many thanks, Nikhil.
Buy Feng Shui Package for Rs. 151/- only, at
http://shopping.rediff.com/shopping/fengshui_mailer.htm
Richard Stallman's Public Lecture 5pm 17th July, at TIFR. Linuxers mailing list Linuxers@mm.ilug-bom.org.in http://mm.ilug-bom.org.in/mailman/listinfo/linuxers
On Wed, 4 Jul 2001, rahil wrote:
considering you want this application (as well as database?) to run off a 286 as well you could look at using this application with a
linux -> 32bit arch, 286 -> 16bit arch. will it work?
Philip
Nikhil,
--- Nikhil Karkera ianmalc@rediffmail.com wrote:
I need to choose a good combination of front & back ends for a database application.
The application is quite simple. It is basically a muster, where employees can sign in by entering an employee-ID.
One possible choice for the backend is PostgreSQL. It has a C interface based on libpq (you'll find it in the documentation) as also an ODBC interface. Your problem will be in the front end, which you say needs to run on legacy 286/ 386 boxen. One possible approach would be to build an interface wrapper around the Postgres backend with libpq, and run a networked client on the 286/ 386 front ends, which you will have to write a customised program for. You'll have no problem running Linux on a 386, and can write a framebuffer or ncurses based front end on it. The 286 is a diferent issue, since ELKS is not mature enough to use in a production environment, and probably does not have most of the features that you will need. Anyway, I believe later versions of MSDOS support TCP/IP, since Microsoft offers a freely downloadable IP stack off their FTP server for MSDOS (I downloaded it a couple of years ago, and it ought to be still around). You could see if you could build your front end with this.
Obvious criticisms of this approach would stem from the excessive overengineering introduced by Postgres for a simple app, but hey, it has a C API, it's free, and it's available! MySQL might be better but I don't know very much about it.
HTH,
Krishnan
__________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/