You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrey Razumovsky (JIRA)" <ji...@apache.org> on 2009/11/11 09:20:39 UTC

[jira] Updated: (CAY-1287) Enchance SQLTemplate API and it's Documentation for forming not-mapping (DataRow) queries

     [ https://issues.apache.org/jira/browse/CAY-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Razumovsky updated CAY-1287:
-----------------------------------

    Fix Version/s:     (was: 3.0)
                   3.1

3.0 cannot have API changes, moving to 3.1

By the way, Evgeny, as Andrus mentioned, classes from o.a.c.query package (any many others, like o.a.c.map) cannot have reference to classes from o.a.c.access because last ones do not exist in cayenne-client jar and not avaliable on ROP

> Enchance SQLTemplate API and it's Documentation for forming not-mapping (DataRow) queries
> -----------------------------------------------------------------------------------------
>
>                 Key: CAY-1287
>                 URL: https://issues.apache.org/jira/browse/CAY-1287
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: Cayenne Core Library, Cayenne Documentation
>    Affects Versions: 2.0 branch
>            Reporter: Evgeny Ryabitskiy
>             Fix For: 3.1
>
>
> I wish to use nice SQLTemplate scripting engine for my simple not-mapping (DataRow) runtime-formed queries.
> But now I should pass a DataObject to SQLTemplate constructor.
> The question is: "For what?"
> To do mapping???
> If my query is like: "SELECT max(id) as MAX_ID from Table1" it has no sense!
> I want to add constructor like: SQLTemplate(String defaultTemplate, Map parameter)
> and teach DataContext to perform such queries well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Updated: (CAY-1287) Enchance SQLTemplate API and it's Documentation for forming not-mapping (DataRow) queries

Posted by Andrus Adamchik <an...@objectstyle.org>.
We had a mailing list discussion, and IIRC the only thing we are doing  
under this Jira is changing documentation. No code changes.

Andrus

On Nov 11, 2009, at 10:20 AM, Andrey Razumovsky (JIRA) wrote:

>
>     [ https://issues.apache.org/jira/browse/CAY-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
>  ]
>
> Andrey Razumovsky updated CAY-1287:
> -----------------------------------
>
>    Fix Version/s:     (was: 3.0)
>                   3.1
>
> 3.0 cannot have API changes, moving to 3.1
>
> By the way, Evgeny, as Andrus mentioned, classes from o.a.c.query  
> package (any many others, like o.a.c.map) cannot have reference to  
> classes from o.a.c.access because last ones do not exist in cayenne- 
> client jar and not avaliable on ROP
>
>> Enchance SQLTemplate API and it's Documentation for forming not- 
>> mapping (DataRow) queries
>> -----------------------------------------------------------------------------------------
>>
>>                Key: CAY-1287
>>                URL: https://issues.apache.org/jira/browse/CAY-1287
>>            Project: Cayenne
>>         Issue Type: Improvement
>>         Components: Cayenne Core Library, Cayenne Documentation
>>   Affects Versions: 2.0 branch
>>           Reporter: Evgeny Ryabitskiy
>>            Fix For: 3.1
>>
>>
>> I wish to use nice SQLTemplate scripting engine for my simple not- 
>> mapping (DataRow) runtime-formed queries.
>> But now I should pass a DataObject to SQLTemplate constructor.
>> The question is: "For what?"
>> To do mapping???
>> If my query is like: "SELECT max(id) as MAX_ID from Table1" it has  
>> no sense!
>> I want to add constructor like: SQLTemplate(String defaultTemplate,  
>> Map parameter)
>> and teach DataContext to perform such queries well.
>
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>