[FRG-259] enhance CREATE FUNCTION to allow for specification of a flag that statement implementations which invoke the function must not be cached

LucidDB / luciddb

DEFUNCT: See README

https://github.com/LucidDB/luciddb

Apache License 2.0

53 stars 24 forks source link

[FRG-259] enhance CREATE FUNCTION to allow for specification of a flag that statement implementations which invoke the function must not be cached #613

Closed dynamobi-build closed 12 years ago

dynamobi-build commented 12 years ago

[reporter="jvs", created="Mon, 12 Mar 2007 15:44:12 -0500 (GMT-05:00)"] See TODO in com.lucidera.farrago.LucidDbPreparingStmt. More use-cases incoming.

dynamobi-build commented 12 years ago

[author="jvs", created="Mon, 12 Mar 2007 15:51:20 -0500 (GMT-05:00)"] We can use the existing non-reserved keyword DYNAMIC_FUNCTION as a modifier in the DDL.

dynamobi-build commented 12 years ago

[author="jvs", created="Mon, 9 Apr 2007 12:00:13 -0500 (GMT-05:00)"]

add boolean attribute dynamicFunction to class Routine in FEM (it's OK to make it mandatory; migration will fill it in as false); this will turn into isDynamicFunction/setDynamicFunction setters/getters on FemRoutine
follow existing pattern for isDeterministic in DDL parsing and validation; it should be OK to specify this attribute for any kind of UDR
create yourself a task in jira.lucidera.com for tracking by Boris
check with Zelaine on where to make model change; FEM has been modified on lcs branch and hasn't been integrated to lu/dev yet

dynamobi-build commented 12 years ago

[author="jvs", created="Mon, 9 Apr 2007 12:11:05 -0500 (GMT-05:00)"] Once you add this flag to the initsql DDL for applib.get_var, it should be OK to remove the existing code-level hack, since we always run CREATE OR REPLACE during LucidDB upgrade.

dynamobi-build commented 12 years ago

[author="schoi", created="Sun, 15 Apr 2007 10:31:36 -0500 (GMT-05:00)"] eigenchange 9110