Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 2.x
-
Component/s: None
-
Security Level: All
-
Labels:None
Description
We should evaluate the current situation of stored procedure support as well as where we want to go with it / how far we want to support it, if at all.
Issue Links
- relates to
-
DDC-391
Allow to specifiy custom Entity and Collection Persister classes
-
Activity
Benjamin Eberlei
made changes -
Roman S. Borschel
made changes -
| Fix Version/s | 2.1 [ 10022 ] |
Benjamin Eberlei
made changes -
| Fix Version/s | 2.x [ 10090 ] | |
| Fix Version/s | 2.1 [ 10022 ] |
Benjamin Eberlei
made changes -
| Workflow | jira [ 11094 ] | jira-feedback [ 13845 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback [ 13845 ] | jira-feedback2 [ 15709 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback2 [ 15709 ] | jira-feedback3 [ 17966 ] |
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
- Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DDC-445, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
I think this relates to the usage of Custom Persisters