google-code-export / s3db

Automatically exported from code.google.com/p/s3db
1 stars 0 forks source link

Retrieve statements corresponding to specific rules. #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
* What is the URL of your deployment?
<http://biodata.mdanderson.org/s3db/>

* What steps will reproduce the problem?
1. Get rule id for 'Researcher' 'has' 'initials'.

[NOTE] Replace KEYNAME with actual key value
$ curl "http://biodata.mdanderson.org/s3db/S3QL.php?
key=KEYNAME&query=<S3QL><from>rules</from><where><project_id>80192</project_id>
</where></S3QL>" | tidy -q -i

If we skim the results (about 65-70% of way down), the associated rule id is 
3705.
This step is purely informational to show how I came up with the rule id used 
in the
next step.

2. Get statements related to R3705:

$ curl "http://biodata.mdanderson.org/s3db/S3QL.php?
key=KEYNAME&query=<S3QL><from>statements</from><where><project_id>80192</proje
ct_id><rule_id>3705</rule_id></where></S3QL>"

* What is the expected output? What do you see instead?

Here's what I get back. All headers and no data.

<TABLE><TR><TD>statement_id</TD><TD>value</TD><TD>notes</TD><TD>file_name</
TD><TD>file_size</TD><TD>rule_id</TD><TD>resource_id</TD><TD>project_id</TD><T
D>created_on</TD><TD>created_by</TD><TD>subject</TD><TD>verb</TD><TD>object<
/TD><TD>description</TD><TD>instance_id</TD><TD>item_id</TD><TD>permission_leve
l</TD><TD>assigned_permission</TD><TD>effective_permission</TD><TD>uid</TD><TD
>uri</TD></TR></TABLE>

I expected to get back results that match the following:

$ curl "http://biodata.mdanderson.org/s3db/S3QL.php?
key=KEYNAME&query=<S3QL><from>statements</from><where><rule_id>3705</rule_id><
/where></S3QL>" | tidy -q -i

* What version of the product are you using? On what operating system?
S3DB 3.5.2 (as of 2009/03/10 when issue reported)
Redhat 5.2

* Please provide any additional information below.

This is the same HTTP GET query that had been working for over a month. So what 
changed 
since 2009/03/04?

Original issue reported on code.google.com by proeb...@mdanderson.org on 10 Mar 2009 at 8:51

GoogleCodeExporter commented 9 years ago
Please see issue 5.

Original comment by helenadeus on 10 Mar 2009 at 9:12