| Key: |
SES-688
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Dmitry Katsubo
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
Sesame
Created: 23/Oct/09 02:33 PM
Updated: 23/Oct/09 02:33 PM
|
|
| Component/s: |
Query Model
|
| Affects Version/s: |
2.2.4
|
| Fix Version/s: |
None
|
|
Generally the idea is to make the query construction more fluent. Ideally I would like to program like this:
{code}
TupleQuery tupleQuery = connection.prepareTupleQuery(DEFAULT_QUERY_LANGUAGE, query);
tupleQuery.setBinding("NAME1", uri).setBinding("NAME2", "data")...;
{code}
For this case the interface should be extended as follows:
{code:title=Query interface}
...
Query setBinding(String name, Value value);
Query setBindings(BindingSet bindingSet);
{code}
Maybe one can benefit from sequencing of {{removeBinding()}}.
The message was created on the basis of [maillist message|http://sourceforge.net/mailarchive/forum.php?thread_name=4ADC839C.3010208%40mail.ru&forum_name=sesame-general].
|
|
|
There are no comments yet on this issue.
|
| |
|
|
Extends Query interface methods