openedge - Structures or javascript/json objects in progress ABL? -


we're migrating 11.6 , think it's great moment rethink old habits , improve concepts.

one of these things way we've been dealing parameter definitions in functions , procedures.

often times have procedures , functions need lot of parameters, either inputs or outputs. personally, readability , maintainability reasons, don't have methods many parameters explicitly declared.

in order avoid problem , still allow large number of parameters, we've manually implemented key-value pair approach single parameter.

but there drawbacks approach:

  • it's not possible tell parameters needed inspecting method signature.
  • you'll need boilerplate code, methods pushing , pulling values.

so said, hear others' thoughts. have ever implemented similar?

is there work javascript/json object in abl?

current implementation.

define variable param character no-undo.  addvalue('id', '1', param). addvalue('date', string(today), param).  run internalproc (input param).

desired implementation

param.id   = 1 param.date = today  run internalproc (input param)

since mentioning 11.6, why not use real class based object (available since 10.1a).

yourpackage\yourparameter.cls:

class yourpackage.yourclass:       define public property date date no-undo      get.     set.       define public property id integer no-undo      get.     set.       constructor public yourclass ():         super ().      end constructor.      constructor public yourclass (pid integer, pdate date):         super ().          assign this-object:id = pid                this-object:date = date .       end constructor.  end class.

and internal procedure:

define input parameter poparameter yourpackage.yourclass no-undo .

and caller:

define variable o yourpackage.yourclass no-undo.  o = new yourpackage.yourclass(). o:id = 42. o:date = today.  run internalproc (o) .

alternative caller:

run internalproc (new yourpackage.yourclass (1, today)) .

the abl provides full oo capabilities 10.1a on , can mixed nicely procedural code. , parameter objects (structs) great way started few inital classes in legacy code.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more