Activity
From 10/26/2018 to 11/24/2018
11/24/2018
- 09:51 PM Database Feature #3759: setup, test and document PostgreSQL on Windows
- As far as I know the MinGW64 has support for @long long int@. it is @__int64@. So what you need to do is to try to de...
11/23/2018
- 02:59 PM Database Feature #3759: setup, test and document PostgreSQL on Windows
- Eugenie Lyzenko wrote:
> Take a look at your @.m2\repository\com\git-hub\maven-nar\nar-maven-plugin\version@ directo... - 12:27 PM Database Feature #3759: setup, test and document PostgreSQL on Windows
- Also checklist for PLJava:
https://tada.github.io/pljava/build/build.html
Nar plugin:
http://maven-nar.github.io/ - 12:24 PM Database Feature #3759: setup, test and document PostgreSQL on Windows
- Ovidiu Maxiniuc wrote:
> After I
> [...]
> the mingw profile is indeed used. However, the issues remain.
Take a... - 11:46 AM Database Feature #3759: setup, test and document PostgreSQL on Windows
- After I...
- 11:44 AM Database Feature #3759: setup, test and document PostgreSQL on Windows
- Eugenie Lyzenko wrote:
> Try to add system variable:
> @MSYSTEM@ to be @MINGW64@
I will try that.
> What versio... - 11:41 AM Database Feature #3759: setup, test and document PostgreSQL on Windows
- Ovidiu Maxiniuc wrote:
> Please find the attached logs from
> [...]
> and
> [...]
>
> I noticed that the @ms... - 06:23 AM Database Feature #3759: setup, test and document PostgreSQL on Windows
- Please find the attached logs from ...
- 09:22 PM Database Feature #3759: setup, test and document PostgreSQL on Windows
- Eugenie: Please review this task and offer any advice about mingw.
- 12:55 PM Conversion Tools Feature #3696: implement Progress AST anti-parser
- 3696a was rebased from trunk 11291. The latest revision is 11338.
- 12:42 PM Conversion Tools Feature #3696: implement Progress AST anti-parser
- n/a
- 11:28 AM Conversion Tools Feature #3696: implement Progress AST anti-parser
- I want to rebase 3696a from the latest trunk. I will rebase in 15 minutes unless there are objections.
- 07:09 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Task branch @3782a@ has been updated for review to revisions @11323@, @11324@.
This is some stable pause point to ...
11/22/2018
- 03:41 PM Database Feature #3759 (WIP): setup, test and document PostgreSQL on Windows
- I am having some difficulties with building PL/Java on Windows. Apparently, msvc profile is selected by Maven. I do n...
- 09:51 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Constantin Asofiei wrote:
> Eugenie, please experiment what happens if there are child frames and the selected elem... - 08:45 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Eugenie, please experiment what happens if there are child frames and the selected elements (to be moved) are not fr...
11/21/2018
- 10:12 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Task branch @3782a@ has been updated for review to revision @11321@.
This update introduces the new approach for W...
11/19/2018
- 03:48 PM Database Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Eric Faulhaber wrote:
> Is this inability to cache limited to the cases which use DYNAMIC-FUNCTION? Or are you sayin... - 03:01 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Something else: the @_oeusertable@ and any other domain type allows any user ID to be specified, even if it does not ...
- 01:05 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Greg Shah wrote:
> Is the @_oslocal@ approach using something like PAM or does it just rely upon the user being alre... - 01:02 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Is the @_oslocal@ approach using something like PAM or does it just rely upon the user being already logged in?
- 12:50 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- These metadata tables define the domains and the domain types:...
11/16/2018
- 03:30 PM Database Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Ovidiu Maxiniuc wrote:
> I see an issue though: doing so will alterate the interpreted AST tree and break the caches... - 03:14 PM Database Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- The problem is that the current implementation of the dynamic queries is too logical in FWD. If the parameters and an...
- 10:13 PM Database Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- In other words, it is treated as a query substitution parameter?
- 02:00 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- After some investigation and design analysis my refactoring plan is(the implementation can be different, this is the ...
- 07:04 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > I'm not sure I've completely got your question. In @JS@ the ...
11/15/2018
- 06:52 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Eugenie Lyzenko wrote:
> Is the @p2j.screen.js@ the main module to capture and handle @JS@ mouse events?
Yes, this... - 06:46 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Eugenie Lyzenko wrote:
> I'm not sure I've completely got your question. In @JS@ the selection boxes are always pain... - 06:43 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Constantin Asofiei wrote:
> Question: when moving/resizing a widget, is it possible to have its selection rectangle ... - 06:35 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Question: when moving/resizing a widget, is it possible to have its selection rectangle drawn behind a widget, while ...
- 06:31 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Questions to clarify:
Is the @p2j.screen.js@ the main module to capture and handle @JS@ mouse events? What is the ... - 10:41 PM User Interface Bug #3597: fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and misc wid...
- Making a review and check for the current status of the direct manipulation functionality to create . The testcases I...
- 02:26 PM Database Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- This is a bit (or more) strange. The combination of dynamic queries and dynamic function call is in fact used as a wo...
- 01:27 PM Base Language Feature #3751: implement support for OO 4GL and structured error handling
- +Class Members Access Summary+
|_. Resource |_. Data Member |_. Default Access Mode |_. PUBLIC |_. PROTECTED |_. P...
11/14/2018
- 04:02 PM Base Language Feature #3751: implement support for OO 4GL and structured error handling
- Comments from a customer 4GL developer:
* ABL garbage collection is based on reference counting.
* The ABL (at le... - 03:49 PM Base Language Feature #3751: implement support for OO 4GL and structured error handling
- Some of the built-in classes provided by OpenEdge are not documented in the 4GL reference PDF. This online doc is a ...
- 03:05 PM Database Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Yes, this is the objective. I will separately send you some example customer code which is supposed to work.
- 03:04 PM Database Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Well, I encountered some strange results. Please confirm that the goal of this task is to add support for constructs ...
- 02:04 PM Database Feature #3761 (WIP): add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Started by creating toy testcases that use DYNAMIC-FUNCTION().
- 02:03 PM Database Feature #3760 (Review): temp-table options
- Added conversion and runtime support for @SERIALIZE-NAME@ attribute. Committed to 3782a/11317.
Automated testing is ... - 09:11 PM User Interface Bug #3597 (WIP): fix direct manipulation problems related to MOVABLE, SELECTED, SELECTABLE and mi...
- Resume working on this branch.
11/13/2018
- 04:22 PM Base Language Feature #3754 (Closed): TRANSACTION resource support
- 04:13 PM Base Language Feature #3754: TRANSACTION resource support
- Branch 3754a was merged to trunk rev 11291 and archived.
- 04:08 PM Base Language Feature #3754: TRANSACTION resource support
- Eric Faulhaber wrote:
> ETF runtime testing passed (full search and dev tests).
Great! I'll release it shortly.
... - 04:00 PM Base Language Feature #3754: TRANSACTION resource support
- Constantin Asofiei wrote:
> Eric: please help me with runtime testing - I don't think full runtime is required, just... - 03:40 PM Base Language Feature #3754: TRANSACTION resource support
- If Eric's tests pass please merge to trunk.
- 03:40 PM Base Language Feature #3754: TRANSACTION resource support
- Code Review Task Branch 3754a Revision 11293
The changes are good. - 02:43 PM Base Language Feature #3754: TRANSACTION resource support
- Greg Shah wrote:
> Do we have sufficient checks to ensure this same limitation is forced?
Now we do - see 3754a rev... - 02:01 PM Base Language Feature #3754: TRANSACTION resource support
- > there is no way for TRANSACTION-MODE AUTOMATIC or TRANS-INIT-PROCEDURE invoked entries to automatically start a fu...
- 01:53 PM Base Language Feature #3754: TRANSACTION resource support
- Greg Shah wrote:
> The part I don't understand is how this is supposed to act when it is called while a full transac... - 11:34 PM Base Language Feature #3754: TRANSACTION resource support
- Code Review Task Branch 3754a Revision 11292
I've reviewed everything, it is very good.
The part I don't unders... - 03:57 PM Database Feature #3760 (WIP): temp-table options
- In all my testcases the @RCODE-INFORMATION@ seems to be implemented. In fact, this is only a legacy keyword (as the d...
- 03:48 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- All of these are classified as "global builtin variables" since they don't take parenthesis. Even though the 4GL doc...
- 03:28 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Greg, why are these marked as VAR_RAW (and registered as global variables) instead of builtin functions, in progress....
- 02:55 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Greg Shah wrote:
> * ENCRYPT
> * DECRYPT
> * GENERATE-RANDOM-KEY()
These are dependent on @SECURITY-POLICY:SYMMET... - 07:13 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- > @EXPORT/IMPORT-PRINCIPAL@ creates a byte representation of the @CLIENT-PRINCIPAL@ resource, returned as a @raw@ ins...
- 08:17 AM Database Feature #3759: setup, test and document PostgreSQL on Windows
- > * Will the database server run on same machine as the FWD server?
Yes.
> * Is there a preferred PostgreSQL ve... - 07:54 AM Database Feature #3759: setup, test and document PostgreSQL on Windows
- A few questions here:
* Will the database server run on same machine as the FWD server?
Theoretically, this shoul...
11/12/2018
- 05:06 PM Base Language Feature #3752: CLIENT-PRINCIPAL resource and other security features
- @EXPORT/IMPORT-PRINCIPAL@ creates a byte representation of the @CLIENT-PRINCIPAL@ resource, returned as a @raw@ insta...
- 05:01 PM Base Language Feature #3752 (WIP): CLIENT-PRINCIPAL resource and other security features
- 04:47 PM Base Language Feature #3754: TRANSACTION resource support
- Greg, 3754a rev 11292 adds:
* full conversion support
* runtime is almost done, I need to do some more manual testi...
11/08/2018
- 04:15 PM Base Language Feature #3741 (Closed): implement complete support for the CALL object handle and related attribu...
- 04:14 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Branch 3741a was merged to trunk rev 11290 and archived.
- 04:03 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> Code Review Task Branch 3741a Revision 11300
>
> I'm good with the changes. You can merge to ... - 04:00 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Code Review Task Branch 3741a Revision 11300
I'm good with the changes. You can merge to trunk when ready. - 12:04 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg, thanks for the idea - I've implemented this in 3741a rev 11300.
11/07/2018
- 06:29 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> Can you use a local @int64@ or @decimal@ subclass for the conversion and then assign back the kno... - 04:23 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Can you use a local @int64@ or @decimal@ subclass for the conversion and then assign back the known-valid value to th...
- 01:29 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> I think the only remaining issue is the @BDT.assignDirect@. It is used for such a limited requir... - 12:31 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Sorry, I see you already did this with #3789. Nice!
- 12:30 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- In regard to #3741-57, I agree it is worth looking into this performance case. Please open another task for this.
- 12:29 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Code Review Task Branch 3741a Revision 11299
The changes are good.
I think the only remaining issue is the @BDT... - 11:29 AM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Note that I couldn't find a way to get rid of the @BaseDataType.assignDirect@ flag - this is still in use.
- 10:17 AM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Rebased 3471a from trunk rev 11289 - new rev 11299.
- 07:34 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg, 3741a rev 11298 contains the final changes related to CALL. I've not included the changes I mentioned in #3741...
- 06:26 PM Base Language Feature #3754: TRANSACTION resource support
- Created task branch 3754a from trunk rev 11289.
Rev 11290 adds full conversion support for @TRANSACTION@ handle an... - 02:59 PM Base Language Feature #3754: TRANSACTION resource support
- There is something interesting related to the TRANSACTION handle:
* this is accessed via @procedure:TRANSACTION@, an... - 02:37 PM Base Language Feature #3754: TRANSACTION resource support
- Yes, that is fine.
- 02:30 PM Base Language Feature #3754: TRANSACTION resource support
- Constantin Asofiei wrote:
> Is it OK to use @TransactionManager.transactionModeAuto()@ for @TRANSACTION-MODE AUTO@ s... - 02:18 PM Base Language Feature #3754: TRANSACTION resource support
- Is it OK to use @TransactionManager.transactionModeAuto()@ for @TRANSACTION-MODE AUTO@ statement?
- 11:13 AM Base Language Feature #3754: TRANSACTION resource support
- Go ahead and add these other features.
> And another note about RUN ... TRANSACTION DISTINCT - can you check the r... - 10:32 AM Base Language Feature #3754: TRANSACTION resource support
- Further reading shows that @RUN ... TRANSACTION DISTINCT@ is used as a fail-safe if 4GL decides to propagate the clie...
- 10:12 AM Base Language Feature #3754: TRANSACTION resource support
- Greg, let me know if I should add these attributes (to allow complete TRANSACTION handle support):
* @IS-OPEN@ attri... - 10:05 AM Base Language Feature #3754: TRANSACTION resource support
- According to this https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/pasoe-migrate-develop/...
- 08:39 AM Base Language Feature #3754 (WIP): TRANSACTION resource support
- 01:24 PM Runtime Infrastructure Feature #3789: rewrite writeObject and readObject to rely on NativeTypeSerializer or a similar ap...
- Another part to think about is the @read/writeObject@ in @Protocol$Reader@ and @Writer@ classes - this uses standard ...
- 11:50 AM Runtime Infrastructure Feature #3789: rewrite writeObject and readObject to rely on NativeTypeSerializer or a similar ap...
- The native array serializing changes are in 3789a rev 11290.
- 11:45 AM Runtime Infrastructure Feature #3789: rewrite writeObject and readObject to rely on NativeTypeSerializer or a similar ap...
- Created task branch 3789a from trunk rev 11289.
This includes an initial approach of using @NativeTypeSerializer@ ... - 11:33 AM Runtime Infrastructure Feature #3789 (New): rewrite writeObject and readObject to rely on NativeTypeSerializer or a simi...
11/01/2018
- 07:12 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- I have a heavy duty test which uses lots of PUT statements - and what 4GL does in 1-2 seconds FWD does in 10 to 30. ...
- 05:14 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Using @getBytes().length@ makes sense.
- 04:49 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Eric, thanks!
Greg: I have another issue, this time in @BinaryData.setString@ - this assumes the number of bytes i... - 04:43 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- 3741a/11295 has passed all ETF testing.
- 03:39 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> If this really creates too much overhead to be included in BDT, then can we pass a wrapper for th... - 03:32 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- No, this will create a huge mess and much confusion.
If this really creates too much overhead to be included in BD... - 03:27 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Eric Faulhaber wrote:
> Eric Faulhaber wrote:
> > ...all temp-tables, and any records held in the JDBC driver...
>... - 03:16 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Eric Faulhaber wrote:
> ...all temp-tables, and any records held in the JDBC driver...
Actually, temp-table recor... - 03:05 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> The @assignDirect@ and @variable@ members of BDT should probably be marked @transient@ so it is c... - 02:59 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- I'm running the last round (batch) now. The other two have passed.
- 02:39 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Eric, the diffs are OK, please go ahead with runtime testing (if you haven't already).
- 02:42 AM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Constantin Asofiei wrote:
> please send me the diffs (or the baseline and converted sources) once you have the conve... - 12:31 PM Database Feature #3758 (WIP): misc database features
- Created task branch 3758a.
- 09:12 AM User Interface Bug #3787 (New): The stack trace window modality deviation
10/31/2018
- 03:39 PM Conversion Tools Feature #3696: implement Progress AST anti-parser
- Rebased 3696a from trunk 11288. The latest revision is now 11307.
- 03:10 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> 1. The @assignDirect@ and @variable@ members of BDT should probably be marked @transient@ so it i... - 12:51 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Code Review Task Branch 3741a Revision 11295
Wow! That is a massive code drop. It took me all morning to review ... - 12:41 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- OK, converting now.
- 11:46 AM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- 3741a rev 11295 fixes some regressions and it passed MAJIC main and conversion testing.
Eric: please go ahead with... - 08:02 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Constantin Asofiei wrote:
> Eric: please let me know if you can help me with ETF testing; you will need to reconvert... - 02:05 PM User Interface Feature #3261 (Review): enhanced browse that can optionally selected as a replacement for the def...
10/30/2018
- 07:39 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- 3741a rev 11293 is under MAJIC testing now.
What is left are to finish the conversion of output parameters and jav... - 05:28 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Indeed, there is one way out before the new block is processed: the @ControlFlowOps.invokeImpl()@ ~ line 3350. Here, ...
- 04:43 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- I'm getting this:...
- 04:34 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- The @TM.deregisterOutputParameterAssigner()@ is called before the call of an procedure/function and native API routin...
- 03:37 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Ovidiu, please help me with something: shouldn't @TM.deregisterOutputParameterAssigner@ be called in case the i.e. RU...
- 01:14 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Applications can't depend upon behavior that abends in the 4GL. It is safe to let it assign. Put notes in the Javad...
- 01:01 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg, documentation states that if the OUTPUT/INPUT-OUTPUT variable is out of scope, then terminate with an error con...
10/29/2018
- 07:43 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Constantin Asofiei wrote:
> Ovidiu, please confirm another possible bug: @BaseDataType.generateDefault@ now generate... - 04:39 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Ovidiu, please confirm another possible bug: @BaseDataType.generateDefault@ now generates an unknown value, as the BD...
- 03:39 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Some other weird things related to @DLL-CALL-TYPE@: if the @LIBRARY@ attribute is not set BEFORE the @SET-PARAMETER@,...
- 02:28 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Forgot about runtime/conversion of:
* extent arguments
* field reference arguments
* by-reference and append argum... - 06:35 AM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Constantin Asofiei wrote:
> Ovidiu, I think there is a bug in @date.assign(BaseDataType)@ - if the current date inst... - 04:07 AM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- An ETA for what is left:
* the @dll-call-type@ - I'll finish this and have a cleaned up version by tomorrow, to put ...
10/26/2018
- 04:38 PM Base Language Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Ovidiu, I think there is a bug in @date.assign(BaseDataType)@ - if the current date instance is unknown and the argum...
Also available in: Atom