On Wed, 2005-02-23 at 16:52 +0200, Markos Charatzas wrote: > Well ofcourse it depends on the scale of the application.
precisely, not necessarily > If you want something quick and dirty you can do it with Velosurf no probs. yes, you can - but even in large applications I'm not totally certain that the choice of Hibernate is always pertinent (it depends if you really need persistence or not). Hence, Velosurf can be a "clean" choice. > I was just trying to alert ppl who might jump straight to the Velosurf wagon > to support their database driven application. seems fair Claude > Markos > > On Wednesday 23 February 2005 14:51, Claude Brisson wrote: > > On Wed, 2005-02-23 at 12:39 +0200, Markos Charatzas wrote: > > > Hm... > > > > > > Im quite skeptical about this... > > > > > > Why not use a "proper" OR mapping tool (e.g. hibernate), provide a > > > complete db implementation (Database, DatabaseRequest, DatabaseClient) > > > and then use a db client wrapper to place as a tool using the velocity > > > toolbox. > > > > What do you mean by "proper"? bigger? ;-) > > do you really mean that hibernate + a wrapper tool would be a proper > > solution? > > > > just curious... > > > > Claude > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
