Jira uses corporate architecture byBiz

"Open to business project" is a corporate infrastructure.

It so happened that Jira uses this, and I was very shocked at how much work involved in extracting data for a particular object (for example, a problem / error in the case of Jira).

Imagine you get a list of all the problems, it must first get all the columns (or properties) to display for the column of the table, and then pull the values โ€‹โ€‹for each. For a corporate solution, this seems like a suboptimal solution (but I understand how it adds flexibility).

You can read how to use it in Jira practically: http://confluence.atlassian.com/display/JIRA/Database+Schema

Main site: http://ofbiz.apache.org/docs/entity.html

I'm just confused how to list all the problems. Sense what sql queries look like?

This is one thing to pull out one problem, but to get a list, you need to do the work to get the values. I donโ€™t think this can be done with a single query using connections now?

+3
source share
3 answers

(Disclaimer: I work for Atlassian, but I'm not on the JIRA team)

OFBiz EE is simply an abstraction layer for moving between database tables and fantastic maps called GenericValues. It does not affect the database schema. Your real problem here seems to be that the JIRA database schema is complex.

, , , , - . . , JIRA .

, , , JIRA API.

, JIRA, - http://forums.atlassian.com/

+6

, jira, ( API), . - , SQL, . , , , . (.. PL/SQL, pgPL/SQL).

0
SELECT * FROM jiraissue;
0
source

Source: https://habr.com/ru/post/1704354/


All Articles