go to post David Van De Griek · Nov 9, 2020 Daniel, I guess it looks like we don't support CodeMode = generator for overriding property methods. CodeMode = code should work, but you need to access type parameters from the property definition in order to generate the proper code. I believe you will need to extend the %String datatype and override Normalize, then use the new datatype class in your property definition. Here is an example: Class User.StringoNoEmpty Extends %String [ Language = objectscript ] { ClassMethod Normalize(%val As %RawString) As %String [ CodeMode = generator, ServerOnly = 1 ] { { set code="%val" if %parameter("TRUNCATE"),%parameter("MAXLEN")'="" { set code="$e(%val,1,"_(+%parameter("MAXLEN"))_")" } $$$GENERATE(" RETURN $tr("_code_",$c(0),"""")") RETURN $$$OK} } Property myString As User.StringoNoEmpty(MAXLEN = 54, TRUNCATE = 1); Hope this helps, -dave
go to post David Van De Griek · Nov 4, 2020 $c(0) is the internal representation of the SQL empty string ''. Your insert must be using '' as the value for myProperty instead of null if you are seeing $c(0) for the field values. SQL null and empty-string string are very different. null means unknown, while empty string is a 0 length string value. If you always want to convert '' to null for myProperty values, write a myPropertyNormalize property member method that converts the value to null. This will override the %String Normalize() method and convert $c(0) to "" whenever the property/field's value is normalized by the filers. Trying to do this in a trigger will not work as triggers are not meant to be used to modify property/field values being filed.
go to post David Van De Griek · Sep 4, 2020 Can you be a little more specific? Are you are asking about embedded SQL, dynamic sql, ODBC, JDBC, or limits for each interface? The answer is different for each, although I'm not sure there is an exact length limit. For embedded SQL, I don't believe there is any limit other than the maximum size of the code you can define for a .MAC routine or class method. I believe for dynamic SQL the max length should be pretty close to the maximum string length supported by your Caché instance. I was able to Prepare a using %SQL.Statement that was a bit over 3,600,000 characters in length (using IRIS, I don't have immediate access to a Caché instance))
go to post David Van De Griek · Feb 19, 2020 Hi Suman, For the case where the ID is not system generated, try the following query after a successful INSERT: SELECT LAST_IDENTITY() You can actually do this for the case where the ID is system generated also, but in that case getGeneratedKeys is probably a better option. LAST_IDENTITY() simply returns the value of the %ROWID variable, which is set after a successful INSERT to the value of the rowid field.
go to post David Van De Griek · Mar 15, 2019 $System.SQL.TODATE() returns a %Date (+$Horolog) value.The second argument to TODATE() describes the input format of the string-date value. In your example, you passed in a MM/DD/YYYY value but told TODATE the format was YYYY-MM-DD.set p="12/03/2019" write $System.SQL.TODATE(p,"DD/MM/YYYY")Would have returned a logical %Date value
go to post David Van De Griek · Mar 6, 2019 Try this:CREATE TABLE test ( identifier VARCHAR(200) NOT NULL, value INTEGER COMPUTEONCHANGE("%%INSERT","%%UPDATE") COMPUTECODE { if %oper="INSERT" { set {*}=1 } elseif %oper="UPDATE" { set {*}={value}+1 } }, PRIMARY KEY (identifier))[SQL]SQL:USER>>select identifier, value from testidentifier value0 Rows(s) Affected[SQL]SQL:USER>>insert or update test (identifier) values ('row 1')1 Row Affected[SQL]SQL:USER>>insert or update test (identifier) values ('row 1')1 Row Affected[SQL]SQL:USER>>insert or update test (identifier) values ('row 2')1 Row Affected[SQL]SQL:USER>>insert or update test (identifier) values ('row 2')1 Row Affected[SQL]SQL:USER>>insert or update test (identifier) values ('row 2')1 Row Affected[SQL]SQL:USER>>insert or update test (identifier) values ('row 3')1 Row Affected[SQL]SQL:USER>>select identifier, value from test identifier valuerow 1 2 row 2 3 row 3 1 3 Rows(s) Affected
go to post David Van De Griek · Mar 5, 2019 1) Primary Key in Caché / IRIS is useful in that you can expose to third-party tools (typically through xDBC catalog queries) what the Primary Key is for your table. Other than that, it has no special meaning to us.2) You can define bitmap indices using Index1 if you tweak the property definition of Identifier to tell the system the value is a positive integer: Property Identifier As %Integer(MINVAL=1)
go to post David Van De Griek · Aug 7, 2018 Once you have the $list value in dat, use $listnext rather than a loop with $listget. For example: set ptr = 0 while $listnext(dat,ptr,value) { <do something with your value in value> }
go to post David Van De Griek · Aug 13, 2017 $system.SQL.TODATE() converts a readable format into a logical %Date value (+$Horolog). $system.SQL.TODATE() does support converting from Julian date to %Date if you use the "J" format. However, there is one issue; the value is returned in YYYY-MM-DD format for dates prior to 1841-01-01. I will make a note to correct this. USER>for Julian=2393465:1:2393475 w !,$SYSTEM.SQL.TODATE(Julian,"J") 1840-12-25 1840-12-26 1840-12-27 1840-12-28 1840-12-29 1840-12-30 0 1 2 3 4 "J"ulain format is also supported for $SYSTEM.SQL.TOCHAR(): USER>set string="2017-08-13" write !,$SYSTEM.SQL.TOCHAR(string,"J") 2457979
go to post David Van De Griek · Sep 21, 2016 This same issue was reported a week or two ago to the WRC.Purging cached queries should clear the issue.It appears to be an issue where the server gets into a state where the cached query class gets an error during creation (that is not reported) and the class is created without any methods. I believe that customer was on version 2014.1. Can you please let us know what version you saw this problem on?Also, if you can reproduce the issue, please contact the WRC with the details. Thank you.Also, %SYS.SQLSRV is a routine, not a class, which is why you could not find information on it in documatic.
