Activity
From 07/25/2019 to 08/23/2019
08/23/2019
- 03:14 PM Feature #3809: ProDataSet support
- Found another issue: bind can be bi-directional, from the destination to source, if the source is BY-REFERENCE. I'm w...
- 09:01 PM Feature #3809: ProDataSet support
- Constantin,
Please see revision 11483. Further stabilized. Now the 8.9MB xml you sent me is read successfully and, w...
08/21/2019
- 06:35 PM Feature #3809: ProDataSet support
- Constantin, please see revision 11479. Further stabilized and with support for indexes and relations.
- 12:03 PM Feature #3809: ProDataSet support
- Constantin, please see revision 11477. I stabilized it so it should handle the simple xml as the one you sent to me.
... - 04:15 AM Feature #3809: ProDataSet support
- Ovidiu, please stabilize and commit your READ-XML changes; as I mentioned before, the urgent part is reading a single...
- 04:46 PM Feature #1587: implement full support for word indexes
- The following are notes about "word break tables" in the 4GL. The tables are a simple mapping between a character an...
- 05:21 AM Support #3871: determine how to change codepages/locales during import
- Greg Shah wrote:
> An underlying assumption of our approach so far is that the definition of a codepage is an intern...
08/20/2019
- 05:58 AM Feature #3809: ProDataSet support
- Constantin Asofiei wrote:
> Ovidiu, when serializing a dataset to JSON, what is the order of the records on a child ...
08/19/2019
- 05:55 PM Feature #3809: ProDataSet support
- Ovidiu, when serializing a dataset to JSON, what is the order of the records on a child table (associated with a pare...
08/16/2019
- 08:32 AM Feature #3809: ProDataSet support
- Ovidiu, after the save-row-changes and the 'next-rowid' in #3809-210, please work on the read/write-xml/json methods....
08/13/2019
- 03:06 AM Feature #3816: table and table handle parameter options
- The changes with the mutable proxy implementation are in 4124a rev 11449. Please review.
08/12/2019
- 04:43 AM Feature #3809: ProDataSet support
- Ovidiu, another question; for a data-source query like:...
- 09:18 PM Feature #3809: ProDataSet support
- Ovidiu, please work on @SAVE-ROW-CHANGES@ with priority.
08/11/2019
- 04:10 PM Feature #3809: ProDataSet support
- There's a problem with a dynamic query:...
08/10/2019
- 12:00 PM Bug #4200: verify and fix all temp-table options which must result in different DMO implementatio...
- TODO: are there places in the runtime where we are using the DMO implementation class legacy annotations directly (as...
- 11:51 AM Bug #4200: verify and fix all temp-table options which must result in different DMO implementatio...
- There was at least a case where FWD was 'losing' a temp-table option or field option, as it was generating a single D...
- 11:47 AM Bug #4200 (New): verify and fix all temp-table options which must result in different DMO impleme...
08/09/2019
- 12:21 PM Feature #3809: ProDataSet support
- Constantin Asofiei wrote:
> Ovidiu, some notes about the DATASET import/export; the current WRITE implementation doe... - 11:05 AM Feature #3809: ProDataSet support
- Ovidiu, some notes about the DATASET import/export; the current WRITE implementation doesn't follow the 'relation tre...
08/08/2019
- 10:25 AM Feature #4176: make certain metadata tables aware of live runtime state
- FWD's current implementation of the @_db@ metadata table is static, holding only information discovered at conversion...
- 10:23 AM Feature #4176 (New): make certain metadata tables aware of live runtime state
- 10:19 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Single user mode of the CONNECT statement is not currently supported. We'll need a test case to understand exactly ho...
- 10:17 AM Feature #4175 (Closed): add support for -1 (single user) option for CONNECT statement
- 10:11 AM Bug #4173: BUFFER-COPY/BUFFER-COMPARE compares table fields by name rather than data type and order
- Based on our findings of how tables are compared for parameter passing purposes and shared temp-table definitions (by...
- 09:25 AM Bug #4173 (Closed): BUFFER-COPY/BUFFER-COMPARE compares table fields by name rather than data typ...
08/07/2019
- 05:23 PM Feature #3809: ProDataSet support
- Constantin Asofiei wrote:
> Considering that this 'fill must have a data-source or before-fill callback' doesn't rai... - 04:22 PM Feature #3809: ProDataSet support
- I think I'm on to something: if the NO-ERROR mode is ON while DATASET:FILL is executed, this gets deactivated if ther...
- 08:01 AM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> There's another issue with BIND which I don't see how to solve yet: if the source and ta...
08/05/2019
- 09:38 AM Feature #3816: table and table handle parameter options
- There's another issue with BIND which I don't see how to solve yet: if the source and target tables have different na...
- 08:33 AM Feature #3816: table and table handle parameter options
- I'll drop here some starting spec on @TABLE@ parameters.
* When a temp-table is defined as @REFERENCE-ONLY@, it ca...
08/03/2019
- 08:25 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> * this 'mutable proxy' must be kept only at the Java field, with the 'original definitio... - 08:15 PM Feature #3816: table and table handle parameter options
- The main changes related to making the Buffer mutable are working, same with the Dataset. But there is some cleanup ...
08/02/2019
- 05:26 PM Feature #3816: table and table handle parameter options
- Ovidiu Maxiniuc wrote:
> We talked about calling an update notification on parent dataset once a buffer was "redirec... - 05:26 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Constantin Asofiei wrote:
> > There's another part related to the field mapping between the... - 05:20 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> There's another part related to the field mapping between the source and target temp-tab... - 05:20 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> There's another part related to the field mapping between the source and target temp-tab... - 05:18 PM Feature #3816: table and table handle parameter options
- There's another part related to the field mapping between the source and target temp-tables: when they are used in qu...
- 04:21 PM Bug #4163: SHARED non-NEW buffer definitions must act as the equivalent of FIND or CREATE
- SHARED non-NEW buffer definitions must promote the buffer and generally act as the equivalent of FIND or CREATE.
... - 04:12 PM Bug #4163 (Closed): SHARED non-NEW buffer definitions must act as the equivalent of FIND or CREATE
08/01/2019
- 06:50 PM Feature #3816: table and table handle parameter options
- Ovidiu, I think the @private-data@ issue I've mentioned is because, even if you have something like @def input parame...
- 06:16 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> Ovidiu, do you know if we currently have a registry of explicitly defined buffers for a ... - 06:02 PM Feature #3816: table and table handle parameter options
- Ovidiu, do you know if we currently have a registry of explicitly defined buffers for a table? I ask because 4GL swi...
- 05:58 PM Feature #3816: table and table handle parameter options
- Something similar to this I added for @StaticDataSet@. There is the @bound@ @Dataset@ which can be @null@ for REFEREN...
- 05:42 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> What exactly would be mutable? The current buffer proxy? Some new wrapper class? Please help... - 05:34 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Hm, I don't know enough about the current DATASET implementation to comment or adjust my pro... - 05:25 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> @bufB@ is a parameter scoped to the called procedure, correct? Doesn't it naturally go out o... - 05:24 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> If we don't make these mutable...
What exactly would be mutable? The current buffer p... - 05:22 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> Eric, I'm backtracking a little on your "@TemporaryBuffer.associate@ will return a new p... - 05:18 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> Eric Faulhaber wrote:
> > Sorry, what precisely are you asking about? The remapped gett... - 04:54 PM Feature #3816: table and table handle parameter options
- Eric, I'm backtracking a little on your "@TemporaryBuffer.associate@ will return a new proxy idea". The reason are t...
- 04:51 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Sorry, what precisely are you asking about? The remapped getter/setter calls in the invocati... - 04:30 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Constantin, Ovidiu, do either of you know of any "4GL resource state" that is managed in @Bu... - 04:22 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Constantin, Ovidiu, do either of you know of any "4GL resource state" that is managed in @Bu... - 04:14 PM Feature #3816: table and table handle parameter options
- Constantin, Ovidiu, do either of you know of any "4GL resource state" that is managed in @BufferImpl@ which does NOT ...
- 04:08 PM Feature #3816: table and table handle parameter options
- I suppose we could create a proxy for all the interfaces which @BufferImpl@ statically implements (including those of...
- 03:53 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Same restriction for @h-ttB:BUFFER-FIELD("fB")@?
Yes, this throws error 7351. However, @h-t... - 03:51 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Ovidiu Maxiniuc wrote:
> > Because the all calls are 'live' redirected to @ttA@ buffer, the... - 03:45 PM Feature #3816: table and table handle parameter options
- Ovidiu Maxiniuc wrote:
> Because the all calls are 'live' redirected to @ttA@ buffer, the changes done on @ttB@ will... - 03:43 PM Feature #3816: table and table handle parameter options
- Marian, what is exactly the difference between passing a structure (I guess DATASETs and BUFFERs are similar here) wi...
- 03:42 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> Will this @BufferImpl@ reflect any changes back to the caller's buffer (@bufA@)? Also, ... - 03:32 PM Feature #3816: table and table handle parameter options
- I think the dynamic dereference can be handled separately. In this case, both @ttB@ and @ttA@ will only have the acce...
- 03:31 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> Eric Faulhaber wrote:
> > Since this is the same object, is my dynamic field dereferenc... - 03:27 PM Feature #3816: table and table handle parameter options
- Ovidiu Maxiniuc wrote:
> I think it might work. The new local BUFFER will keep the reference of the passed-in BUFFER... - 03:16 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Since this is the same object, is my dynamic field dereference scenario 2 described in #3816... - 03:15 PM Feature #3816: table and table handle parameter options
- I think it might work. The new local BUFFER will keep the reference of the passed-in BUFFER and will delegate all met...
- 03:13 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> @TB.associate@ returns @<T>@, where @<T>@ is a reference to the *locally* defined buffer (i.... - 02:51 PM Feature #3816: table and table handle parameter options
- Thanks, Marian. I think my design will handle the BY-REFERENCE case, which is complicated a bit by the fact that FWD ...
- 02:39 PM Feature #3816: table and table handle parameter options
- I don't know much about how you have that implemented but a temp-table is a data structure in 4gl, it has a default b...
- 01:28 PM Feature #3816: table and table handle parameter options
- As I understand it, there are 3 cases of field dereferencing within the callee procedure, which need to be supported ...
- 12:08 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Potential complication: since the field names can differ for the same fields (i.e., those wh... - 12:07 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Instead of returning @void@, @TemporaryBuffer.associate@ returns @<T>@, where @<T>@ is a buf... - 12:02 PM Feature #3816: table and table handle parameter options
- Guys, what do you think about this approach?
Instead of returning @void@, @TemporaryBuffer.associate@ returns @<T>... - 10:56 AM Feature #3816: table and table handle parameter options
- Sorry, I was not very explicit because I reached some of the conclusion while writing the note. Here is an more compl...
- 09:06 AM Feature #3816: table and table handle parameter options
- > Actually the indexes must be a match.
I wonder if my testing was previously somehow incorrect or not extensive e... - 08:26 AM Feature #3816: table and table handle parameter options
- Actually the indexes must be a match.
I tried to run the following test procedure:... - 08:56 PM Feature #3815: more temp-table options
- Fixes for remaining CODEPAGE issues are in 3816a rev 11327.
07/31/2019
- 07:57 PM Feature #3816: table and table handle parameter options
- > The source and target buffers must match only on the number of fields and their types (in the proper order), as far...
- 06:35 PM Feature #3816: table and table handle parameter options
- A few questions on your last post...
What happens if @ttB@ does not match the structure (i.e., type and order of f... - 03:30 PM Feature #3816: table and table handle parameter options
- The mess is getting even messier. The source and target buffers must match only on the number of fields and their ty...
- 02:42 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Hm, I just realized @BufferImpl@ inherits all the instance data from @HandleChain@ and its a... - 02:33 PM Feature #3816: table and table handle parameter options
- Hm, I just realized @BufferImpl@ inherits all the instance data from @HandleChain@ and its ancestry. This plan is get...
- 02:32 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
>... so I need some guidance as to whether the core design idea of doing this at the proxy lev... - 02:29 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> Eric Faulhaber wrote:
> > In terms of FWD's implementation, if we needed to "un-assign"... - 02:14 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> In terms of FWD's implementation, if we needed to "un-assign" the buffer (i.e., invocation h... - 02:01 PM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> Also, another unknown is what happens with the buffer's referenced record, for the impli... - 01:33 PM Feature #3816: table and table handle parameter options
- I should clarify that last statement. The proxy instance also holds instance data which @BufferImpl@ (the proxy's par...
- 01:25 PM Feature #3816: table and table handle parameter options
- Hm, I was thinking of making the proxy itself mutable, but the only instance data the proxy holds is the invocation h...
- 01:15 PM Feature #3816: table and table handle parameter options
- Eric Faulhaber wrote:
> Do we need the ability to re-associate a different @RecordBuffer@ instance with a @Buffer@ p... - 01:00 PM Feature #3816: table and table handle parameter options
- Constantin, et al.: what are we thinking, in terms of an implementation of BY-REFERENCE for buffers in FWD?
Do we ... - 06:30 PM Feature #3809: ProDataSet support
- Constantin, please see revision 11409.
- 05:07 PM Feature #3809: ProDataSet support
- Constantin Asofiei wrote:
> Does this fix the BY-REFERENCE, too? I mean, any DATASET can be replaced by an argument ... - 05:03 PM Feature #3809: ProDataSet support
- Ovidiu Maxiniuc wrote:
> Support for REFERENCE-ONLY option and NUM-REFERENCES attribute of DATASET was added in the ... - 04:41 PM Feature #3809: ProDataSet support
- Support for REFERENCE-ONLY option and NUM-REFERENCES attribute of DATASET was added in the branch 4124a.
Committed r...
07/29/2019
- 06:22 PM Feature #3816: table and table handle parameter options
- > I can 'emulate' certain features (like ensuring the buffer is on the same record, when entering and exiting a proce...
- 04:51 AM Feature #3816: table and table handle parameter options
- I'm just saying there is no real dependency between @REFERENCE-ONLY@ and @BY-REFERENCE@. For @BIND@ however one of th...
- 04:20 AM Feature #3816: table and table handle parameter options
- Marian Edu wrote:
> Constantin, are you referring to @BY-REFERENCE@ here? @REFERENCE-ONLY@ is just an option on temp... - 04:00 AM Feature #3816: table and table handle parameter options
- Constantin Asofiei wrote:
> Next issue I need solved is REFERENCE-ONLY for DATASET and TEMP-TABLE: these really are ...
07/28/2019
- 02:05 PM Feature #3816: table and table handle parameter options
- Next issue I need solved is REFERENCE-ONLY for DATASET and TEMP-TABLE: these really are the same resources as, for ex...
07/26/2019
- 03:22 PM Feature #3809: ProDataSet support
- Branch 4124a was updated with following changes:
* @BufferImpl@ has SET-CALLBACK methods implemented;
* @DataSet@ p... - 02:08 PM Feature #3815: more temp-table options
- > Is @def shared temp-table tt-one@ in the same source file as @def temp-table tt-like like tt-one.@?
No, they ar... - 01:21 PM Feature #3815: more temp-table options
- > But I don't know if @tempTableRef@ really needs to be @null@ for non-master buffers - if this is true, and it can b...
- 09:38 AM Feature #3815: more temp-table options
- Constantin Asofiei wrote:
> Ovidiu/Stanislav: we need to determine how the @TemporaryBuffer.tempTableRef@ is behaves... - 07:59 AM Feature #3815: more temp-table options
- Ovidiu/Stanislav: we need to determine how the @TemporaryBuffer.tempTableRef@ is behaves. For @master != null@, I fo...
- 07:20 AM Feature #3815: more temp-table options
- > The problem is that the entries in the SVM.tempTables registry are keyed by converted name, not legacy name. I supp...
- 04:40 AM Feature #3815: more temp-table options
- > I need to take a look again. If it's only about the adding a new map, it should be resolved quickly.
Actually th... - 11:55 AM Feature #4155: remove conversion dependency on metadata .df file
- FWD currently parses a metadata @.df@ file exported from the data dictionary as part of early schema dictionary proce...
- 11:45 AM Feature #4155 (WIP): remove conversion dependency on metadata .df file
- 09:40 AM Feature #3816: table and table handle parameter options
- Ovidiu Maxiniuc wrote:
> Can you add more detail? Why is it incorrect?
See the changes in 4124a rev 11384. The ide... - 09:26 AM Feature #3816: table and table handle parameter options
- Can you add more detail? Why is it incorrect?
- 02:42 AM Feature #3816: table and table handle parameter options
- The current approach with datasets, where a @OUTPUT dsHandle BY-REFERENCE@ argument is passed to a @OUTPUT DATASET@ p...
07/25/2019
- 12:47 PM Feature #3816: table and table handle parameter options
- Stanislav Lomany wrote:
> # When a temp-table is defined as @REFERENCE-ONLY@, it cannot be used until it is initiali... - 11:15 AM Feature #3816: table and table handle parameter options
- Stanislav Lomany wrote:
> I like the idea of a buffer being mutable, because it solves all of the issues above. An...
Also available in: Atom