You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Thomas Vandahl (JIRA)" <ji...@apache.org> on 2007/08/23 22:20:31 UTC

[jira] Resolved: (TORQUE-95) MapBuilder.vm should have the platform dependency removed

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

Thomas Vandahl resolved TORQUE-95.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.3-RC3

Fixed in SVN. The decision is now made at runtime.

> MapBuilder.vm should have the platform dependency removed
> ---------------------------------------------------------
>
>                 Key: TORQUE-95
>                 URL: https://issues.apache.org/jira/browse/TORQUE-95
>             Project: Torque
>          Issue Type: Improvement
>          Components: Generator
>    Affects Versions: 3.3-RC2
>            Reporter: Thomas Vandahl
>            Assignee: Thomas Vandahl
>            Priority: Minor
>             Fix For: 3.3-RC3
>
>
> This is more a marker issue to improve the platform independence of Torque. In the OM templates I found that the only point left where platform-dependent code is generated is MapBuilder.vm  There, tMap.setPrimaryKeyMethodInfo() is set depending on the selected database platform. If that could be removed/changed, the generated classes would be free of platform dependent code which in turn would allow to switch between database backends without re-generating the OM-classes.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org