[GLLUG] Best Web/Desktop Programming solution (...)

[Eric Miller]

If a lot of people are going to be hitting the database at the same time
I'd avoid loading up the stored procedures with business logic if
possible. I'd try to build a business layer that is portable between the
desktop and web applications. Of course the exact definition for "a lot
of people" depends on the environment, hardware, database server, etc.

On Tue, 2005-04-19 at 11:36 -0400, Benjamin Minshall wrote:
> Jason Green wrote:
> > At the risk of starting a major flame war, I'm going to post this 
> > question just to get some outside perspectives...
> > 
> > The IT Department at my company (all 3 of us) is looking to slowly 
> > migrate away from our Access 2000 platform to something web-based and 
> > ...
> > 
> 
> You may really want to consider PostgreSQL as the database backend to 
> make use of the superior stored procedure capabilities and complete 
> transaction capabilities.
> 
> I really, really recommend that your program logic be stored procedures 
> in the database.  That way you can slap together as many different GUI, 
> web, palm pilot, "whatever" interfaces you want to the same application 
> and they will all handle your data exactly the same way.  Also you can 
> have your good programmer(s) write the program logic, and the good 
> designer(s) write the GUI/web without trampling on each other.
> 
> Good luck, it sounds like you have a lot of work ahead of you!
> 
> -Ben
> _______________________________________________
> linux-user mailing list
> linux-user at egr.msu.edu
> http://www.egr.msu.edu/mailman/listinfo/linux-user