Activity

From 05/13/2022 to 06/11/2022

06/11/2022

08:34 PM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: Constantin, please let me know when it is a good time to commit my changes (note that a full reconversion is required... Ovidiu Maxiniuc

06/10/2022

03:20 PM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: Yes, it is possible that some attributes can be changed between @create-like@ and @temp-table-prepare@.
Ovidiu Maxiniuc
12:48 PM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: Another idea for CREATE-LIKE: does this actually build a dynamic DMO? Why not reuse the source DMO, as multiplexing w... Constantin Asofiei
12:41 PM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: Constantin Asofiei wrote:
> Ovidiu Maxiniuc wrote:
> > Next time a new table is created using a very similar struct... Ovidiu Maxiniuc
02:29 AM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: Ovidiu Maxiniuc wrote:
> Next time a new table is created using a very similar structure the @cache@ in @DynamicTabl... Constantin Asofiei
08:20 PM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: I encountered an incorrect optimization issue. Assume we create a copy of a dataset. It will use the @DynamicTablesHe... Ovidiu Maxiniuc

06/09/2022

12:40 PM Feature #4516: testing and completion of runtime compatibility for table/table-handle/dataset/dat...: Another fix for OUTPUT DATASET-HANDLE ... BY-REFERENCE - copy directly the callee's dataset - is in 6129a/13937. Constantin Asofiei
06:13 AM Feature #4516: testing and completion of runtime compatibility for table/table-handle/dataset/dat...: An attempt at a fix for a @OUTPUT TABLE tt1 BIND@ where @tt1@ is @REFERENCE-ONLY@ is in 6129a/13936 Constantin Asofiei
10:46 PM Feature #6507: cross-database joins: Some customers have the need to join tables which exist in separate databases in queries outside of FWD, as in:
<p... Eric Faulhaber
10:35 PM Feature #6507 (New): cross-database joins: Eric Faulhaber
09:42 PM Feature #6348: implement support for MariaDB: UTF8MB4 support will be needed. Greg Shah
09:16 PM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: From my tests, so far, the @namespace-URI@ and @namespace-prefix@ attributes are incorrectly copied in 6128a/13934. (... Ovidiu Maxiniuc
09:10 PM Feature #6414: ERROR attribute for buffer, dataset and temp-table: Sometimes the usage of error attribute is incorrectly wired using the compiler wrapper. I have the conversion changes... Ovidiu Maxiniuc
08:01 PM Feature #6414: ERROR attribute for buffer, dataset and temp-table: Ovidiu: What is the status of this one? Greg Shah

06/08/2022

04:55 AM Bug #6503: READ-XML automatically populates fields from NESTED relations: A first pass at the fix is in 6129a/13935 - Ovidiu, please review.
What remains is more tests, like:
* tests with... Constantin Asofiei
04:26 AM Bug #6503: READ-XML automatically populates fields from NESTED relations: This test shows that a nested relation automatically allows populating the child table fields, from the parent table:... Constantin Asofiei
04:18 AM Bug #6503 (New): READ-XML automatically populates fields from NESTED relations: Constantin Asofiei
02:25 AM Feature #6479: pending DISCONNECT and static buffers: My understanding is that a database can't be disconnected if there is at least a buffer attached to it - static or dy... Constantin Asofiei
02:12 AM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: 6128a/13934 adds unknown protection to the temp-table options copy. Constantin Asofiei
02:01 AM Bug #6502: DATASET:CREATE-LIKE copies temp-table options (like XML-NODE-NAME), while TEMP-TABLE:C...: A fix is in 6129a/13933. Ovidiu, please do more tests and confirm this is OK (see the TODOs in the fix). Constantin Asofiei

06/01/2022

04:28 PM Bug #6478: validate arguments for DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NEXT-VALUE: Ovidiu Maxiniuc wrote:
> I understand. In this case the lowercase keys are required.
Please ensure that 'sequences'... Constantin Asofiei
04:15 PM Bug #6478: validate arguments for DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NEXT-VALUE: I understand. In this case the lowercase keys are required. Ovidiu Maxiniuc
03:16 PM Bug #6478: validate arguments for DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NEXT-VALUE: Ovidiu Maxiniuc wrote:
> Constantin Asofiei wrote:
> > Ovidiu, the sequence names should be lowercased in the map.
... Constantin Asofiei
03:14 PM Bug #6478: validate arguments for DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NEXT-VALUE: Constantin Asofiei wrote:
> Ovidiu, the sequence names should be lowercased in the map.
The sequence sql-name shoul... Ovidiu Maxiniuc
03:03 PM Bug #6478: validate arguments for DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NEXT-VALUE: Ovidiu, the sequence names should be lowercased in the map, see this patch:... Constantin Asofiei
03:12 PM Feature #6479: pending DISCONNECT and static buffers: The latest patch is this:... Constantin Asofiei
02:57 AM Feature #6479: pending DISCONNECT and static buffers: And considering that static buffers are associated with a legacy class instance (which is the equivalent of a persist... Constantin Asofiei
02:05 AM Feature #6479: pending DISCONNECT and static buffers: The issue is not just about static buffers - we need a reference counter, as the pending disconnect is possible with ... Constantin Asofiei

05/31/2022

05:46 PM Bug #6478 (WIP): validate arguments for DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NEXT...: Fixed various aspects related to sequences:
* Added validation for specific methods. Extracted common code in worker... Ovidiu Maxiniuc
09:21 AM Bug #6478: validate arguments for DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NEXT-VALUE: Ovidiu, argument validation is not implemented for any of the DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NE... Constantin Asofiei
09:20 AM Bug #6478 (Test): validate arguments for DYNAMIC-CURRENT-VALUE, DYNAMIC-SET-VALUE and DYNAMIC-NEX...: Constantin Asofiei
03:23 PM Feature #6479: pending DISCONNECT and static buffers: The only solution is to mark any buffer defined as a static class member or in a static method as 'static', at Record... Constantin Asofiei
03:14 PM Feature #6479: pending DISCONNECT and static buffers: From #6277-163, by Constantin:
Found the root cause: https://knowledgebase.progress.com/articles/Article/P141997
... Greg Shah
03:13 PM Feature #6479: pending DISCONNECT and static buffers: From #6277-162, by Constantin:
But, the weird thing happens: for a .cls, if the database is connected when the leg... Greg Shah
03:12 PM Feature #6479 (New): pending DISCONNECT and static buffers: Greg Shah

05/30/2022

09:58 AM Bug #6475: double-check and fix any read/write-xml/json issues at table and dataset: This task is to confirm all serialization options at dataset, table and fields (like @serialize-name@, @xml-node-name... Constantin Asofiei
09:56 AM Bug #6475 (New): double-check and fix any read/write-xml/json issues at table and dataset: Constantin Asofiei

05/28/2022

11:09 AM Feature #6371: implement SAVE CACHE statement: This is mostly a development-time activity. Both customer use cases that we know about are less about the runtime na... Greg Shah

05/27/2022

05:51 PM Feature #6453: temp-table features: I remember putting some effort in NAMESPACE-URI and NAMESPACE-PREFIX implementation. They were working for my testcas... Ovidiu Maxiniuc
10:09 AM Feature #6453: temp-table features: * @DEFINE TEMP-TABLE@
** table options @NAMESPACE-URI@ and @NAMESPACE-PREFIX@ are marked runtime partial
** field o... Eric Faulhaber
10:08 AM Feature #6453 (Closed): temp-table features: Eric Faulhaber
05:35 PM Feature #6371: implement SAVE CACHE statement: Greg Shah wrote:
> > In the absence of this, we would need to compare the new schema state against its previous stat... Eric Faulhaber
05:50 AM Feature #6371: implement SAVE CACHE statement: > In the absence of this, we would need to compare the new schema state against its previous state and figure out the... Greg Shah
11:30 PM Feature #6371: implement SAVE CACHE statement: With SAVE CACHE as our notification hook that something has changed in the database's schema, we would need to respon... Eric Faulhaber
04:43 PM Support #6462 (Rejected): additional testing of table parameters: This is a duplicate of #4516. Greg Shah
04:41 PM Support #6462 (Rejected): additional testing of table parameters: Eric Faulhaber
04:42 PM Support #6461 (Rejected): testing of REPLICATION triggers: This is a duplicate of #4376. Greg Shah
04:33 PM Support #6461 (Rejected): testing of REPLICATION triggers: Eric Faulhaber
02:45 PM Feature #6459: query features: Implement and improve the following:
* @QUERY@ handle
** @FIRST-OF@, @LAST-OF@ methods (gap marked none/none) - A... Eric Faulhaber
12:59 PM Feature #6459 (New): query features: Eric Faulhaber
12:24 PM Bug #6458: ensure that OO expressions resolve to query substitution parameters, like handle-based...: We need to create test cases with OO expressions in the WHERE clause of a query/FIND/FOR/etc., which does not referen... Eric Faulhaber
12:20 PM Bug #6458 (Closed): ensure that OO expressions resolve to query substitution parameters, like han...: Eric Faulhaber
12:17 PM Feature #6457: finish COPY-LOB support: The remaining work:
* Encoding behavior needs better testing (at least #6623 must be fixed).
* BOM handling for f... Eric Faulhaber
12:16 PM Feature #6457 (Closed): finish COPY-LOB support: Eric Faulhaber
10:24 AM Support #6455: XML feature(s) needing testing: The @READ-XMLSCHEMA@ method is gap marked as runtime partial but should be listed as basic (just needs some testing). Eric Faulhaber
10:23 AM Support #6455 (Closed): XML feature(s) needing testing: Eric Faulhaber
10:18 AM Feature #6454: database informational features: The following features need implementation/improvement:
* @DBPARAM@ builtin function - not all @CONNECT@ params re... Eric Faulhaber
10:14 AM Feature #6454 (Review): database informational features: Eric Faulhaber
10:00 AM Feature #6450: buffer/buffer-field features: We need to add support for the following (according to gap marking):
* @BUFFER@ handle usage
** @PRIMARY@ attribu... Eric Faulhaber
09:56 AM Feature #6450 (Closed): buffer/buffer-field features: Eric Faulhaber
10:00 AM Feature #6449: review SET-DB-CLIENT() function implementation: Eric Faulhaber wrote:
> This feature is marked (in gap marking) as having partial runtime support. What is left to i... Igor Skornyakov
09:45 AM Feature #6449: review SET-DB-CLIENT() function implementation: This feature is marked (in gap marking) as having partial runtime support. What is left to implement to make this ful... Eric Faulhaber
09:44 AM Feature #6449 (New): review SET-DB-CLIENT() function implementation: Eric Faulhaber
09:41 AM Feature #6448: make location of LOB files configurable for import: Currently, the location is hard-coded to a @lobs@ sub-directory of the directory containing the @.d@ files. Eric Faulhaber
09:41 AM Feature #6448 (Closed): make location of LOB files configurable for import: Eric Faulhaber
02:24 AM Feature #6444: dataset improvements: The following areas need to be implemented or improved:
* @DATA-RELATION@ attributes @RECURSIVE@, @FOREIGN-KEY-HID... Eric Faulhaber
02:21 AM Feature #6444 (Closed): dataset improvements: Eric Faulhaber
01:07 AM Feature #6442: missing encoding/collation features: The following need to be implemented:
* @DBCODEPAGE()@ built-in function
* @DBCOLLATION()@ built-in function
* t... Eric Faulhaber
01:06 AM Feature #6442 (WIP): missing encoding/collation features: Eric Faulhaber
12:53 AM Feature #6441: compatible collation for UTF-8 databases: We currently match legacy database collation for non-UTF-8 databases (at least for Linux-based PostgreSQL) by install... Eric Faulhaber
12:46 AM Feature #6441 (New): compatible collation for UTF-8 databases: Eric Faulhaber
09:05 PM Feature #6348: implement support for MariaDB: | Subqueries / Subselects | Full support | https://mariadb.com/kb/en/subqueries/ |
| JOINs (inner and outer) | Full ... Ovidiu Maxiniuc

05/26/2022

03:52 PM Feature #6418: represent extent fields as arrays: If it represents a significant improvement (in performance or at least in the SQL that accesses these tables), then w... Greg Shah
03:49 PM Feature #6418: represent extent fields as arrays: Our current support for extent fields is to
* (default) normalize each set of extent fields of the same extent _N_... Eric Faulhaber
03:23 PM Feature #6418 (WIP): represent extent fields as arrays: Eric Faulhaber
11:43 AM Feature #6414: ERROR attribute for buffer, dataset and temp-table: Although we generally have full support for ERROR-STATUS:ERROR, the ERROR attribute also exists for buffer, dataset a... Greg Shah
11:34 AM Feature #6414 (Closed): ERROR attribute for buffer, dataset and temp-table: Greg Shah

05/23/2022

11:44 AM Feature #6348: implement support for MariaDB: I am interested in taking this as a background task. I worked previously with MySQL so the syntax should be familiar. Ovidiu Maxiniuc

05/20/2022

02:45 PM Bug #6385: Problem with conversion of REPOSITION TO ROWID with UNKNOWN literal for rowid: The statement @REPOSITION <query> TO ROWID ? NO-ERROR@ is converted to @silent(() -> <query>.repositionByID(new unkno... Igor Skornyakov
02:44 PM Bug #6385 (WIP): Problem with conversion of REPOSITION TO ROWID with UNKNOWN literal for rowid: Igor Skornyakov
07:47 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): > I don't see this conversion problem for OO in current projects, and if this appears at runtime, then it can be fixe... Greg Shah
12:33 AM Feature #6347 (Review): change the name conversion to provide a configurable option to not emit "...: Implemented in 6129a/13860.
Adds a new, optional @conversion@ attribute to the @schema/namespace@ XML element in @... Eric Faulhaber

05/19/2022

10:28 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): Greg Shah wrote:
> It gives type-safety (as much as the 4GL allows) and also would allow overloading.
Yes, this is ... Constantin Asofiei
09:03 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): It gives type-safety (as much as the 4GL allows) and also would allow overloading.
But it would require a good bit... Greg Shah
09:02 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): Exactly. Greg Shah
08:54 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): Greg Shah wrote:
> > And the conversion will just have field1, field2, instead of 'cost', 'price', etc?
>
> Not i... Constantin Asofiei
08:52 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): > And the conversion will just have field1, field2, instead of 'cost', 'price', etc?
Not in the business logic. W... Greg Shah
08:46 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): Greg Shah wrote:
> The idea is that the super-interface would not care about names. It would have a field 1 that is... Constantin Asofiei
08:43 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): The idea is that the super-interface would not care about names. It would have a field 1 that is the correct type an... Greg Shah
08:18 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): Greg Shah wrote:
> My idea was that it would be unpacked as a concreate instance of the right DMO, but internally it... Constantin Asofiei
08:15 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): > I don't think it helps if we add a generic structural type that matches both DMO types. - if you set this at the pa... Greg Shah
03:56 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): Actually, for temp-tables, we emit @TableParameter@ and not the buffer. So this is why it can be handled at runtime.... Constantin Asofiei
03:50 AM Feature #6379: buffer parameters can work as structural matches (without field name matching): Greg Shah wrote:
> The problem here is that our type is too specific. We really need a generic structural type that... Constantin Asofiei

05/18/2022

07:00 PM Feature #6379: buffer parameters can work as structural matches (without field name matching): Eric wrote some testcases and I extended them and checked them into the old testcases project (see @uast/buffer_param... Greg Shah
06:24 PM Feature #6379 (New): buffer parameters can work as structural matches (without field name matching): Greg Shah
02:42 PM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": Eric Faulhaber wrote:
> But perhaps that _is_ the way to do it. From what I understand you are saying, the active pr... Constantin Asofiei
02:22 PM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": Constantin Asofiei wrote:
> Eric, please confirm that your issue is with the 'middle' part, where the schemas/p2os a... Eric Faulhaber
02:16 PM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": Yes, I think the schema/namespace configuration should only be defined once, in the default profile, and the individu... Eric Faulhaber
02:00 PM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": And something else to note: considering that a schema can be part of multiple profiles, I don't think is correct to k... Constantin Asofiei
01:48 PM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": The idea with the conversion profiles was that you are splitting the 4GL converted source code in unique sets, with e... Constantin Asofiei
01:42 PM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": Eric, please confirm that your issue is with the 'middle' part, where the schemas/p2os are processed.
If yes, we h... Constantin Asofiei
01:29 PM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": Eric, the default profile is meant to be 'switched' with the file's profile, when TRPL code is ran (see @config.withF... Constantin Asofiei
12:55 PM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": Ovidiu, Constantin, with the addition of the profiles feature in @p2j.cfg.xml@, what is the appropriate way now to ch... Eric Faulhaber

05/17/2022

10:51 AM Feature #4369: implement stateless FWD server clustering: Evidently REDIS also has an object synchronization capability. We should evaluate this in addition to the other fram... Greg Shah
10:02 AM Feature #6371: implement SAVE CACHE statement: To be clear: we are not planning to support the idea of saving this cache into a binary file and sharing it across se... Greg Shah
09:41 AM Feature #6371: implement SAVE CACHE statement: The @SAVE CACHE@ language statement allows schema changes to be made to a live database and will read the latest chan... Greg Shah
09:29 AM Feature #6371 (Closed): implement SAVE CACHE statement: Greg Shah
09:58 AM Feature #6372: add a 4GL syntax extension to drop a database table while the database is online/t...: To delete a table in the OE database, it requires that the application is stopped and no connections are active to th... Greg Shah
09:53 AM Feature #6372 (New): add a 4GL syntax extension to drop a database table while the database is on...: Greg Shah

05/13/2022

11:35 AM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": > I am leaning toward p2j.cfg.xml
Agreed. Greg Shah
10:59 AM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": I am considering the best place to add this configuration. Currently, we configure persistence name conversion inform... Eric Faulhaber
10:45 AM Feature #6347: change the name conversion to provide a configurable option to not emit "snake case": The intention is to keep names verbetim except for reserved SQL keywords, hyphens and other invalid SQL name constructs. Greg Shah

« Previous

Also available in: Atom

Project

General

Profile

FWD » Core Development » Database

Activity

Activity

06/11/2022

06/10/2022

06/09/2022

06/08/2022

06/07/2022

06/06/2022

06/04/2022

06/03/2022

06/02/2022

06/01/2022

05/31/2022

05/30/2022

05/28/2022

05/27/2022

05/26/2022

05/23/2022

05/20/2022

05/19/2022

05/18/2022

05/17/2022

05/13/2022