[jira] Created: (TORQUE-91) Index-column size attribute is documented but does not work

[Thomas Vandahl (JIRA)]

Index-column size attribute is documented but does not work
---

 Key: TORQUE-91
 URL: https://issues.apache.org/jira/browse/TORQUE-91
 Project: Torque
  Issue Type: Bug
  Components: Generator
Affects Versions: 3.3-RC2
Reporter: Thomas Vandahl
Priority: Minor


The database schema allows a size attribute for the index-column element 
which did not make it into neither the Index code nor the templates. Some 
databases support this parameter, however (namely MySQL). The attribute should 
be utilized where supported by the database.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)

[Scott Eade]

Scott Eade wrote:
Unfortunately I have also run into problems with the work around which 
was using your ACSYaafiComponentService class and Yaafi.  This one is 
even more enigmatic than the ECM issue - I cannot even say that it 
relates to the mentioned configuration, all I know is that when I 
deployed to production the system would after some time become 
unresponsive (no problems are apparent in my development and staging 
environments and the problem is certainly not load related).  I have 
nothing whatsoever to go on - very frustrating.  Anyway, this is a 
totally different issue.
FYI: The issue partially described here turned out to be totally 
unrelated to Turbine and Yaafi - I have now switched back to 
ACSYaafiComponentService and it is working like a charm.


As I have mentioned previously, it would be good to increase the 
visibility of this class.


Scott

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]