[Laszlo-dev] For your review: Laszlo Database API spec version 1.1

[Mika Göckel]

Hi!

I beg your pardon if my question seems heretical, but just for me to 
understand, what direction you are heading to.

I develop Java/J2EE apps since a couple of years now and we avoid low 
level sql wherever possible. We use Object Relational mapping tools like 
Hibernate.
Would it not be a good idea just to put such a framework into the server 
and

a) let people declarde their mapping in hbm.xml style
or
b) do runtime database to java reengineering (like for example middlegen 
does with ant task) and provide this as an object model to the client side?

You get a bunch of dialects of different databases for free, you get a 
pluggable Caching system for free, you avoid the low level type hassle, 
you avoid sql-injection completely, provide a generic Exception Wrapper 
system to avoid people having to deal with db-specific error codes (with 
Spring)... etc.

Ok, HQL instead of SQL would mean a learning curve for some people, but 
with a completely new API there would be a learning curve anyway? (And 
they would not even need to do HQL, because Hibernate can select 'by 
example')

Today, I use JavaRPC in my laszlo project to get a reference to a 
prepopulated FacadeObject in session context to access a Hibernate 
powered backend.
Okay, I don't declare my objects in the client, because I need to have 
the model in the backend anyway to expose it as WebService to other 
systems.

Just my thoughts :-)

Cheers, Mika

--------------------------------------------------
cyber:con gmbh
Rathausallee 10
53757 Sankt Augustin
Germany

www.cybercon.de

Geert Bevin schrieb:

> Hi Max,
>
> I'm still wondering why you put SQL inside the model. If you only  
> declare abstract methods with arguments, what use it is to have SQL  
> attached to it?
>
> I also have another remark, I think you should formalize the types  
> that are supported for the fields and standardize again on a standard  
> set for this and reduce the DB-specific types (like text for  
> example). Some material:
> http://java.sun.com/j2se/1.5.0/docs/guide/jdbc/getstart/mapping.html
> http://www.faqs.org/docs/ppbook/x2632.htm
>
> I also have trouble of seeing why Callbacks should be specified in  
> the spec. Isn't that totally server-side?
>
> About protection against SQL injection, isn't it possible to handle  
> this transparently on the server-side?
>
> Best regards,
>
> Geert
>
> On 4-nov-05, at 02:26, Max Carlson wrote:
>
>> Hi,
>>
>> I'd like your feedback on the attached revised spec.  Thanks to  
>> Henry and Geert for setting me straight on the need for native  
>> methods and a more extensible syntax for specifying constraints.   
>> This time I'm sending out versions with and without revision  
>> tracking on so you can easily see the parts that changed, but still  
>> have a readable version. Let me know how it looks.  Once again, I  
>> look forward to
>> hearing your thoughts and feedback!
>>
>> Regards,
>> Max Carlson
>> OpenLaszlo
>>
>>
>> <database connector spec 11-03-05 norevs.pdf>
>> <database connector spec 11-03-05.pdf>
>> _______________________________________________
>> Laszlo-dev mailing list
>> Laszlo-dev at openlaszlo.org
>> http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
>
>
>
> -- 
> Geert Bevin                       Uwyn bvba
> "Use what you need"               Avenue de Scailmont 34
> http://www.uwyn.com               7170 Manage, Belgium
> gbevin[remove] at uwyn dot com    Tel +32 64 84 80 03
>
> PGP Fingerprint : 4E21 6399 CD9E A384 6619  719A C8F4 D40D 309F D6A9
> Public PGP key  : available at servers pgp.mit.edu, wwwkeys.pgp.net
>
>
> _______________________________________________
> Laszlo-dev mailing list
> Laszlo-dev at openlaszlo.org
> http://www.openlaszlo.org/mailman/listinfo/laszlo-dev