Details
-
Type:
New Feature
-
Status:
In Progress
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Security Level: All
-
Labels:None
Description
I'm not sure if this is really possible..
but to improve performance we should consider generate custom entity persisters.
Now entity persister are not cached,
if we generate it, we can create performance improvement in hidrators, avoiding checks and sql generation every time that an persister is called.
Activity
Fabio B. Silva
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Priority | Major [ 3 ] | Minor [ 4 ] |
Fabio B. Silva
made changes -
| Assignee | Benjamin Eberlei [ beberlei ] | Fabio B. Silva [ fabio.bat.silva ] |
Benjamin Eberlei
made changes -
| Workflow | jira [ 13796 ] | jira-feedback [ 14085 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback [ 14085 ] | jira-feedback2 [ 15949 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback2 [ 15949 ] | jira-feedback3 [ 18196 ] |
Fabio B. Silva
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
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-1889, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
This should be relatively easy in the first step by ust generate the RSM and SQL statements in the constructor and extending from the default persister.