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
Ebean ORM
Home
+ new post
About this group
Join this group
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
 
florin.g  
View profile  
 More options May 19 2009, 2:32 am
From: "florin.g" <florin.gheorgh...@gmail.com>
Date: Mon, 18 May 2009 23:32:07 -0700 (PDT)
Local: Tues, May 19 2009 2:32 am
Subject: Re: Simplifying Ebean Internals ... by Removing MapBean fuctionality (and DB meta data use)
Print | View thread | Show original | Report this message | Find messages by this author
Query only. I'd use any alternative provided. I definitely need this
feature and I appreciate it to be considered.

Thanks for the good work.

On May 18, 6:59 pm, rob bygrave <rbygr...@yahoo.com> wrote:

> > Well, I do use MapBean.

> Do you use MapBean for insert update delete ... or just queries?

> Queries is easy... and doesn't really need the DB meta data. I imagine it is useful to people as it provides a simple low tech way to use any SQL query so I would like to keep MapBean query functionality.

> MapBean is aware of primary keys and version columns plus generated properties like "inserted timestamp", "last update timestamp". So for Insert/Update/Delete MapBeans are aware of concurrency checking and maintaining the version columns etc.

> So, specifically it is the insert/update/delete of MapBeans that makes significant use of the DB meta data. One option is to remove the concurrency checking and automatic management of generated properties like "inserted timestamp" and "last update timestamp".... or just keep MapBeans as they are and make sure the DB meta data is available to support them.

> > Will there be an alternative?

> The query support is easy to keep. The IUD of MapBeans without db meta data is the tricky bit. If people are using MapBeans for IUD now... then that functionality should not be removed in my opinion.


 
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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google