Bug 259330 - [Query] Support transient objects to be passed between client <-> server
Summary: [Query] Support transient objects to be passed between client <-> server
Status: NEW
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-18 19:30 EST by Simon Mc Duff CLA
Modified: 2020-12-11 10:47 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Mc Duff CLA 2008-12-18 19:30:06 EST
Comment 1 Andre Dietisheim CLA 2008-12-22 08:12:09 EST 
what's the usecase here?
Comment 2 Simon Mc Duff CLA 2008-12-22 08:29:51 EST 
(In reply to comment #1)
> what's the usecase here?
> 

I have so far two use cases:

1- My parameter for the query is very complex. It takes Object that are modelled. These instances doesn't need to be persisted but only valid for the query time. Right now you could only push objects that are persisted. (Client->server)

2- The result of the query are objects that are temporary created by the server. Again I don't want to create them for nothing. (Server->client). 

I'm currently developping an application that needs that feature. So it will probably be implemented soon.

Simon
Comment 3 Andre Dietisheim CLA 2008-12-22 09:20:48 EST 
(In reply to comment #2)
> (In reply to comment #1)
> > what's the usecase here?
> > 
> 
> I have so far two use cases:
> 
> 1- My parameter for the query is very complex. It takes Object that are
> modelled. These instances doesn't need to be persisted but only valid for the
> query time. Right now you could only push objects that are persisted.
> (Client->server)
> 
> 2- The result of the query are objects that are temporary created by the
> server. Again I don't want to create them for nothing. (Server->client). 
> 
> I'm currently developping an application that needs that feature. So it will
> probably be implemented soon.
> 
> Simon
> 

great! I thought about this use case for my prototype earlier this year. Unfortunately I forgot what it was about.
Comment 4 Eike Stepper CLA 2009-11-01 05:59:47 EST 
Rebasing all unresolved enhancement requests to 3.0
Comment 5 Eike Stepper CLA 2010-06-29 04:50:53 EDT 
Rebasing all outstanding enhancements requests to version 4.0
Comment 6 Eike Stepper CLA 2011-06-23 03:58:31 EDT 
Moving all open enhancement requests to 4.1
Comment 7 Eike Stepper CLA 2012-08-14 22:56:55 EDT 
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Comment 8 Eike Stepper CLA 2013-06-27 04:07:49 EDT 
Moving all outstanding enhancements to 4.3
Comment 9 Eike Stepper CLA 2014-08-19 09:26:28 EDT 
Moving all open enhancement requests to 4.4
Comment 10 Eike Stepper CLA 2014-08-19 09:36:33 EDT 
Moving all open enhancement requests to 4.4
Comment 11 Eike Stepper CLA 2015-07-14 02:20:25 EDT 
Moving all open bugzillas to 4.5.
Comment 12 Eike Stepper CLA 2016-07-31 01:03:05 EDT 
Moving all unaddressed bugzillas to 4.6.
Comment 13 Eike Stepper CLA 2017-12-28 01:13:15 EST 
Moving all open bugs to 4.7
Comment 14 Eike Stepper CLA 2019-11-08 02:06:06 EST 
Moving all unresolved issues to version 4.8-
Comment 15 Eike Stepper CLA 2019-12-13 12:53:09 EST 
Moving all unresolved issues to version 4.9
Comment 16 Eike Stepper CLA 2020-12-11 10:47:18 EST 
Moving to 4.13.