[
https://issues.apache.org/jira/browse/DERBY-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3570:
---------------------------------
Attachment: derby-3570-01-ab-introduceDeterminismField.diff
Thanks for the feedback Knut and Dag. Attaching
derby-3570-01-ab-introduceDeterminismField.diff. This changes the previous
patch as follows:
1) Fixes the comments on the sqlOptions field as Dag recommended.
A couple other issues:
2) It's true that the SQL modes in sqlOptions could be described by only 2
bits. I gave a couple other bits to that field to account for future expansion.
3) I do intend to add upgrade tests for this work. They will be easier to add
once I introduce some more language. The crude checks which I perform in
GeneratedColumnTest right now can't be performed in the upgrade tests easily
because I get a ClassCastException when I try to retrieve a
RoutineAliasDescriptor out of a down-rev database.
> Implement DETERMINISTIC keyword for procedures and functions
> ------------------------------------------------------------
>
> Key: DERBY-3570
> URL: https://issues.apache.org/jira/browse/DERBY-3570
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Reporter: Rick Hillegas
> Attachments: derby-3570-01-aa-introduceDeterminismField.diff,
> derby-3570-01-ab-introduceDeterminismField.diff
>
>
> We will need DETERMINISTIC functions when we implement generated columns
> (DERBY-481). The syntax and behavior of the DETERMINISTIC keyword are defined
> in the functional spec attached to DERBY-481.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
