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
- Log in to post comments
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 ];
![]()
![]()
As long as you don't go for Sharding this might work quite well.
For Sharding the whole storage environment will make a significant difference also in class definitions.
I tried it now in Caché 2016.2.2 manually overwriting Storage <Type>%Storage.Persistent</Type>.
During compilation it gets automatically set back to <Type>%Library.CacheStorage</Type>
Also in class defintion.
Does this automatic change go back to repository ???
At first sight in Documatic, it looks like
was just renamed to
As a workaround, I would simply try in Caché to make a copy of %Library.CacheStorage to a new %Storage.Persistent
(a pure rename) Then compile a class with one and the other and compare the generated .int code.
It's a dirty hack. ![]()
But I have no hope ISC will ever provide some backward port from IRIS to Caché.
Sorry I have no IRIS at hands and can't try it myself.
score
-1 #1 - disagree, see no valid reasoning
-2 #2 - strongly disagree
-1 #3 - disagree because of #2
+1 #4- agree
+1 #5 - agree
+1 #6 - agree . pls.send enhancement req. to engineering
+0 #7 - not clear about the message ? an oref is neither primitive nor dynamic
+0 #8 - miss imagination of inconsistent return types
+0 #9 - don't understand that message
You may try WebTerminal over HTTPS as an alternate way for access.
It's really a matter of taste.
If you don't like the long list of params (especially with lousy documented methods) you can
#1) use 1 single param and pass a local array byRef . and decode it yourself eg:
do ##class(my.par).method(.par)or
#2) use the traditional style you may know from Caché I/O Device Guide having also just 1 parameter
do ##class(my.pieces).method("/SERVER=127.0.0.1:/PORT=1972:/NAMESPACE=SAMPLES")I personally prefer #2) as it gives you an embedded doc on your intentions.
#1) all documentation on XML is here
It covers everything to output Objects to XML.
#2) to fill this in-between object you may use the SQL Table represented by an object class.
as simple INSERT INTO my.xmltable select .........
You just have to take care that the object class also extends %XML.Adapter .
That makes it ready for XML Export. All details described in docs
Dear Martin,
I have a rather clear vision where your $example comes from ($zzg, $zza, ...) ![]()
My personal suggestion is to move everything you maintain today in %ZZLANG?00 routines into clean Macro definitions (.inc)
The history of %LANG* code goes back to times when migration from other language dialects (MSM, DTM, DSM, VISOS, ..) happened
and developers were writing just in .INT routines. That's far back in the late 80ies. The availability of MACRO code (also ages back) made it almost obsolete. The feature was never eliminated by considerations of backward compatibility.
I personally would never allow any developer to touch %SYS.
And wouldn't accept any code using $zz* , zz* stuff or $zu().
There are much cleaner ways to achieve the same result without compromising the core.
You may take my previous article The 'unlimited' UNIQUE index as a suggestion how to work around this limit.
if you just look for a specific property instead of a larger part of the object
you may use
set value=##class(ICT.Experiments.B).<propertyname>GetStored(primaryKey)
instead of
set collB=##class(ICT.Experiments.B).%OpenId(primaryKey)
to avoid loading the full object
I may misunderstand your intentions but
when I use "ResultSet.%Get("Collection")", all I get is a list of the primary keys of the objects.
now you all you miss for each PrimaryKey is
Set collB=##class(ICT.Experiments.B).%OpenId(primaryKey)
or
Set collC=##class(ICT.Experiments.C).%OpenId(primaryKey)
and the object is yours.
With your class definition, PrimaryKey is the Idkey of the Object.
the total size is somewhat strange its format changes from 255 to 256 in size and interpretation
and again at 65535 / 65536 up to <MAXSTRING>
special case:
the structure of $LB() is rather simply a binary string
-----------element--------------
TotalLength = 1, 3, 7 bytes depending on size *corrected*
Type = 1 byte (check in JSON converter for codes, or just check with ZZDUMP)
Content : size = TotalLength-1-size of length field
-----------element--------------
TotalLength = 1, 3, 7 bytes depending on size *corrected*
Type = 1 byte (check in JSON converter for codes, or just check with ZZDUMP)
Content : size= TotalLength-1-size of length field
-----------element--------------
...
Therefore concatenation of $lb) is so easy
Sorry, I had more changes.
My approach in details
compiles this routine:
and the using class
compiled as
and the test
Well, the code generator can be tricky.
It's not one of my favorites. But sometimes you have no choice.
instead of
do %code.WriteLine($c(9) _ "Quit ..Test()")use
do %code.WriteLine($c(9) _ "Quit zTest()")It worked for me best
OK.
StorageTo../..ToStorage only works in persistent classes where you move content from/to globals.
No chance without storage.
It doesn't get called in Registered Classes and not when the object wasn't saved.
see my test with %Persistent
This proves that there is limited use of the approach.
I could imagine inheriting standard data types for a customized data type and then
adding methods LogicalToStorage and StorageToLogical similar as LogicalToObs, ....
So your manipulations happen on the way from Global to the local variable.
Additional Parameters eventually may control the generated code.
It's just a vague idea.
Ken Olson , the founder of DEC (Digital Equipment Corp.) was famous for its statement:
Similar in the late 1950ies IBM estimated the worldwide market for computers of 15..30 systems in total.
So lack of phantasy what could be in the future is quite common also for very successful people and companies.