normally there is no need for such "wrapper"
typically %Save() returns a %Status object and then it's up to you to analyze it in case there is an error.
In the situation described here, all you can do is just a retry.
- it could be a Lock collision
- or the LockTable is full.
Instead of fiddling in system parameters requiring a restart, you just wait and retry.
if you are curious how often this happens you may add a loop counter. for further decisions
Yes.
it prevents an error message if there is a collision.
if nobody else is around it just falls through without loop.
for an insert you may need and exclusive lock for your table
do {
set gotit=##class(my.class).%LockExtent()
if 'gotit hang .3
} while 'gotit
;; now do your INSERT
and don't forget
do ##class(my.class).%UnLockExtent(0,1)after your insert.
other: XMLSPy for XML/XSD/DTD editing
of course I also use Caché Studio
straight Notepad
Notpad++ especially for JS also some XML if XMLSpy is to heavy
Docs of $G say
| variable | A local variable, global variable, or process-private global variable, subscripted or unsubscripted. The variable may be undefined. variable may be specified as a multidimensional object property with the syntax obj.property. |
similar Docs of $D say
| variable | The variable whose status is to be checked. A local or global variable, subscripted or unsubscripted. The variable may be undefined. You cannot specify a simple object property reference as variable; you can specify a multidimensional property reference as variable with the syntax obj.property. |
but Title in your case is $li(^CinemaooFilmD(3),1). So neither $G() nor $D() is approriate.
misunderstanding:
I suggested to just use that EXAMPLE method to write a HTML structured table.
Variation is in the SQL statement that you pass to it
ClassMethod any(sqlStatement as %string) As %Status {
set query = ##class(%ResultSet).%New() ,
sc = query.Prepare(sqlStatement)
......
}In docs you find Persistent Objects and Caché SQL
especially storage definitions
For more information on the globals used for persistent classes, see “Globals.”
some dirty trick to copy across namespace boundaries:
have a target class config but change the global references in STORAGE section from
^Package.ClassD and ^Package.ClassI to
^|"namespace"|Package.ClassD and ^|"namespace"|Package.ClassI
Might be a different way to work across namespaces
Assuming you get the call string as the variable parameter then
for par="SERVER","PORT","NAMESPACE" set @par=$P($P(parameter,par_"=",2),":") zw @par
SERVER="127.0.0.1"
PORT=1972
NAMESPACE="SAMPLES"Sorry you didn't publish the definition of color .
so assuming it is a $LB( ) structure $LISTTOSTRING(color,',') may cover your needs. It's an SQLFUNCTION too!
just LIST(color) is wrong as it produces a comma-separated list of MULTIPLE records.
you can delete the class in Studio or from SMPortal.
so you delete the class DEFINITION and the related table DEFINITION. but no data.
BUT.
DROP TABLE in SQL also deletes the data AND the definition because this is part of SQL Standard. (Se also MySQL)
I'd suggest you take some time to really read the documentation or consume some online training.
" In MySQL, a "view" is just a saved SQL query - dropping a view does not drop data.
I never imagined dropping the class (which I thought was just a view) would empty the global.
The global was still there, but all the data was gone. "
Caché is different from MySQL but has also VIEWS and dropping a View doesn't touch any Data
But identical as in MySQL DROP TABLE deletes the data.
from http://www.mysqltutorial.org/mysql-drop-table
The DROP TABLE statement removes a table and its data permanently from the database.
and this was your question:
So how else do I drop the table?
and later:
I did one by DDL
if you use DROP without option %NODELDATA your data are gone.
https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_droptable
Short Caché Basics:
so having 3 'tables' on the same global is just having 3 views of the same house.
Recommend readings: Long Caché Basics and Introduction to Caché SQL
IF you have seen the "Light weight Excel" and its Open Exchange Repository
then all you have to do is
- open your file
- use your file
execute OnPage method (from example or your personal variation of it)
- close your file
BINGO!
to make it easier the referred method here:
ClassMethod OnPage() As %Status
{
set sqlStatement="SELECT TOP 23 ID,Name,%ODBCOUT(DOB) DOB,SSN FROM Sample.Person"
,query = ##class(%ResultSet).%New()
,sc = query.Prepare(sqlStatement)
set:sc sc=query.Execute()
quit:'sc sc
set cols=query.GetColumnCount()
write "<table border=1>",!,"<tr>"
for col=1:1:cols {
write "<th align=left><b>"_query.GetColumnHeader(col)_"</b></th>"
}
while query.Next() {
write "</tr>",!,"<tr>"
for col=1:1:cols {
write "<td>"_query.GetData(col)_"</td>"
}
}
write "</tr>",!,"</table>"
quit $$$OK
}OK. I experienced that scenario quite often. 
Suggestion to verify that indices will help you.
- Take a typical class definition, make a copy without storage definition (or remove it)
- compile it with Chaché Default storage and run INSERT INTO new.table SELECT * from old.table a flat table scan
- verify the new table against your needs.
- if it fits then the problem has moved to "update frequency" which might be easier to solve.
It's, of course, limited to the critical tables and not the whole DB
In your case, you have to KILL the underlying globals manually.
As seen in Storage definition
eg. <Global>^SVK</Global> and all others too that you didn't publish
What I've seen so far DDL enabling might not fit your expectations because of that ancient mapping.
(looks like late 80ties or before)
You shouldn't be so much concerned on looping the RecordSet
INSERT ...... SELECT ....
looks smaller and smarter but does basically the same
Well the code you posted shows a rather ancient type of table mapping away from standards.
And the errors you got underlines this as standard methods like %BuildIndices and %PurgeiIndices are not implemented.
I see 3 possible options:
- you find in the code (not necessarily in the class definition) some method to (re) generate the indices.
Without experience with Caché and Object Script a rather impossible task.
- you create a copy of the class definition and move all data there by INSERT INTO new.table SELECT * from old.table
but it is unclear from what you showed to us if INSERT into your table is supported at all
- least risky. you out-comment all broken indices except [IDKEY] and just use a flat table scan.
this is a fast workaround at the price of a poor performance on bigger tables.
honestly. - not a funny situation
You gave the answer already!
By compilation, you DEFINE indexes at their rules.
But you need to generate their content separately by ClassMethod
in each class.
Or from management portal.
.png)
Then they are ready to use.
There is another way directly with SQL
First, you CREATE a temporary table according to your needs (or have it ready)
CREATE GLOBAL TEMPORARY TABLE MyTemp.Table temp1, temp2, . . . . .
Next, you fill it by INSERT directly from SELECT
The select is the same as before.
give your anchor tag an ID and modify it using some JS script.
or use %ZEN.Auxiliary.locatorLink or any other element that allows a HREF.
or trigger it with JS from any onclick event or similar.
It's not much ZEN but pure JS
Hola Francisco !
Málaga is a splendid place.
I was there several times privately (with all related sightseeing) and on business.
Always a great experience!
I wish my Spanish (reading) was not so rusted to assist in tranlsation of articles.
especially this one Uso de expresiones regulares en ObjectScript
Bienvenido, Robert
Independent of the way how your servers are linked It might be the easiest to have SOAP service to call each other passing the lab episode number '1119102928' as a parameter.
If a lock exists it will be removed. if not nothing happens.
Studio has an easy to use SOAP wizard to create the Server and Client part.
Francisco,
instead of FOR EACH which obviously uses a nonexisting Next method
you could create a loop using <WHILE> and do a "manual" loop.
For the condition source.retorno.datos.polizas.poliza.%Size() gives you the index limit
and source.retorno.datos.polizas.poliza.%Get(idx).sucursal .... and similar provides the content.
You have to increment idx manually and it runs from 0 (zero!) to %Size()-1
It's not as elegant as <foreach> but you have control over your JSON input.
You can get the pid without iteration.
|nsp| is only required for access to a lock in a different namespace.
as you describe if you refer to a file outside Caché and Caché has no control over it
it's a clear case of data inconsistency
you have 4 options:
1a) create a fake file at that reference an delete it then
1b) add an "on before delete" trigger to check and fix in advance either in the record or in file system
2a) manipulate the file reference using the object behind your entry
2b) do the delete at object level, trap the error and ignore it. since the file is gone anyway
when you generate Classes from XSD you require a reference. That' s where xsd is stored. It may make sense to ich copy it first to your default repository and generate your classes after.
In fact, I see not 1 but 2 tables that share the same global.
so it might be easier to have 2 separated definitions one with and the other without the 4th subscript (some $h)
for access with SQL you than can use a UNION to assemble them. like:
SELECT * FROM (
SELECT Account, PGC, Entity, ' ' as DateTime, ..fields... FROM TAB1 WHERE <some condition >
UNION ALL
SELECT Account, PGC, Entity, DateTime, ..same as above... FROM TAB2 WHERE <same condition >
) order by 1,2,3,4or you decide to add the missing subscript in your global to have a common structure
Thank you Dan!
So after years, I realized what the proper use of [ Identity ] is.
It's well documented . Anyhow it passed my attention.
Thanks for the clarification.
If this is Caché standard ID it is projected to SQL as xDBC Type INTEGER
Caché SQL Reference - Data Types says:
| INTEGER | %Library.Integer (MAXVAL=2147483647, MINVAL=-2147483648) |
so 5983658923646 is definitely out of range
xDBC Type :
|
BIGINT |
%Library.BigInt |
represents a 64 bit integer value.
I'm not aware of any parameter to change the data type of the generated ID.
But this hack may do the trick. Just add this calculated Property to your class without affecting the storage.
Property myID As %BigInt [ Calculated, SqlComputeCode = { set {*}=%ID}, SqlComputed ];