Strange behaviour

[csbrogi]

Hello
ok here is my data

Code: Select all

mysql> describe me_references;
+----------+-------------+------+-----+---------+-------+
| Field    | Type        | Null | Key | Default | Extra |
+----------+-------------+------+-----+---------+-------+
| Name     | varchar(32) | YES  |     | NULL    |       |
| SourceID | int(11)     | NO   |     | NULL    |       |
| TargetID | int(11)     | NO   |     | NULL    |       |
+----------+-------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

mysql> describe modelelement;
+---------------+---------------+------+-----+---------+-------+
| Field         | Type          | Null | Key | Default | Extra |
+---------------+---------------+------+-----+---------+-------+
| Name          | varchar(32)   | YES  |     | NULL    |       |
| Spezifikation | varchar(1024) | YES  |     | NULL    |       |
| Stereotyp     | varchar(32)   | YES  |     | NULL    |       |
| ME_ID         | int(11)       | NO   | PRI | NULL    |       |
| Parent_ID     | int(11)       | YES  |     | NULL    |       |
+---------------+---------------+------+-----+---------+-------+
5 rows in set (0.00 sec)


mysql> select * from me_references;
+-----------+----------+----------+
| Name      | SourceID | TargetID |
+-----------+----------+----------+
| uc1->req1 |        3 |        6 |
| uc2->req2 |        4 |        7 |
+-----------+----------+----------+
2 rows in set (0.00 sec)

mysql> select * from modelelement;
+---------------+-----------------------------------+-------------+-------+-----------+
| Name          | Spezifikation                     | Stereotyp   | ME_ID | Parent_ID |
+---------------+-----------------------------------+-------------+-------+-----------+
| Root Package  | This is the spec of package       | package     |     1 |      NULL |
| Sub Package   | This is the spec of sub package   | subpackage  |     2 |         1 |
| Use Case 1    | This is the spec of useCase 1     | useCase     |     3 |         2 |
| Use Case 2    | This is the spec of useCase 2     | useCase     |     4 |         2 |
| Use Case 3    | This is the spec of useCase 3     | useCase     |     5 |         2 |
| Requirement 1 | This is the spec of requirement 1 | requirement |     6 |         2 |
| Requirement 2 | This is the spec of requirement 2 | requirement |     7 |         2 |
+---------------+-----------------------------------+-------------+-------+-----------+
7 rows in set (0.00 sec)

I attace three reports MYSQL_Test1.mrt is the target report, but this results in an empty document
MYSQL_Test3.mrt is the first step working, but without using the subreport
MYSQL_Test2.mrt is for control only and lists the references and the targets

As in the long long thread before, the document should look like something like

Code: Select all

package Root Package

  subpackage Sub Package

      useCase Use Case 1
     This is the spec of use case 1
     Requirement 1
     This is the spec of requirement 1

     useCase Use Case 2
     This is the spec of use case 2
     Requirement 2
     This is the spec of requirement 2

     useCase Use Case 2
     This is the spec of use case 2

[HighAley]

Hello.

I attace three reports MYSQL_Test1.mrt is the target report, but this results in an empty document
MYSQL_Test3.mrt is the first step working, but without using the subreport
MYSQL_Test2.mrt is for control only and lists the references and the targets

As in the long long thread before, the document should look like something like

You've got a loop. The problem in the MYSQL_Test1.mrt file is that you use relation from modelelement to me_references and backward.

Please look at the attached report.

Thank you.

[csbrogi]

Hello,
thanks for your reply, but my intention is to navigate from "use case 1" to "requirement 1" and display the specification of "requirement 1". And your example doesn't achive this. The core of my question in this threat is if navigation between data in the same "data table" is possible.
And you said in your post on
10 Jul 2012 12:12:

It is hard to say. Probably yes, if you set the structure, relations between the tables, then yes - it will be better.

And the aim of my test was to find out wether navigation works better using a database as data-source. And obviously it doesn' t. (quod erat demonstrandum)

Regards,
Clemens

[HighAley]

Hello,
thanks for your reply, but my intention is to navigate from "use case 1" to "requirement 1" and display the specification of "requirement 1". And your example doesn't achive this. The core of my question in this threat is if navigation between data in the same "data table" is possible.
And you said in your post on
10 Jul 2012 12:12:

It is hard to say. Probably yes, if you set the structure, relations between the tables, then yes - it will be better.

And the aim of my test was to find out wether navigation works better using a database as data-source. And obviously it doesn' t. (quod erat demonstrandum)

What do you mean under navigation?
If to change your data, the report could be more simpler.
Please, try to set the Parent_ID of the Requirement 1 to 3 and of the Requirement 2 to 4.
Then try to use next report is there what do you need?

Thank you.

[csbrogi]

Hello,

it's a workaround but being able to able to display one element (in my case "requirement") below "use case" without using the hierarchical data band, since using hierarchies forces me to adjust my input data to the structure of the output but I prefer defining the structure of my document in the report template, since this is easier for an user to modify.
Using Hierarchies is a kind of work around, the other is using diffferent tables for all element types.

Thanks for looking at my problem,


Regards
Clemens

[HighAley]

Hello.

it's a workaround but being able to able to display one element (in my case "requirement") below "use case" without using the hierarchical data band, since using hierarchies forces me to adjust my input data to the structure of the output but I prefer defining the structure of my document in the report template, since this is easier for an user to modify.
Using Hierarchies is a kind of work around, the other is using diffferent tables for all element types.

If you can't change your input data then you should create a new data source from other data source.
Please, look at the attached report template.

Thank you.

[csbrogi]

Hello,

using different datasource may be a solution although there will be situations where it is necessary to navigate an element of the same datasource.

Thanks
Clemens

[HighAley]

Hello, Clemens.

using different datasource may be a solution although there will be situations where it is necessary to navigate an element of the same datasource.

What are you understand under "navigate"?
Do you still have any problems?

Thank you.

[csbrogi]

Hello,

What are you understand under "navigate"?
Do you still have any problems?

navigate means display information from one Data-Table (for example ModelElement) and then display information about another element (typically ModelElement, too), related to this Element by some information form the data-source.In my example it's display the specification text of "requirement 1" below "use case 1".
Being able to display this information directly would be great, but I hope I get around this problem (not to say navigate around it ) by the means discussed:
- using hierarchical databand
- using different data sources.

Regards,
Clemens

[HighAley]

Hello.

So we found a solution for your problem.
Let us know if you'll have any problems else.

Thank you.