Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion Simplifying Ebean Internals ... by Removing MapBean fuctionality (and DB meta data use)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Apoptosis  
View profile  
 More options May 16 2009, 10:28 pm
From: Apoptosis <jacob.champ...@gmail.com>
Date: Sat, 16 May 2009 19:28:58 -0700 (PDT)
Local: Sat, May 16 2009 10:28 pm
Subject: Re: Simplifying Ebean Internals ... by Removing MapBean fuctionality (and DB meta data use)
Just my 2 cents.  I read your forum post on this topic, and it seems
your doing this all for DDL generation.  I have been a java programmer
for 11 years 10 of which have been Java/SQL and I have never generated
my schema from my java beans.  Java objects always seems to need work
around existing schemas.  Put another way the Relation Database rules
the world no mater what the OO purists think.  I would be hard pressed
to remove flexibility for existing schemas for DDL generation.  This
is actually one of the reasons I am attracted to EBean, it seems to be
more DB centric instead of Object centric like Hibernate.  Especially
in the Query language.  No Restrictions and Projections and Criteria.
Good ol reliable Queries.

Jacob


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.