Activity
From 04/02/2021 to 05/01/2021
04/30/2021
- 04:23 PM Feature #3814: more schema metadata
- > Code review 3814a rev 12304-12307, part 2.
>
> *Functional:*
>
> I understand your term for persisting the st... - 07:25 AM Feature #3814: more schema metadata
- I've noticed one more discrepancy between 4GL and FWD.
If a record is updated twice w/o commit like this:... - 03:51 AM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> The root cause of the double-counting of the retrieve statistic is that we are setting the r...
04/29/2021
- 06:36 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> Eric Faulhaber wrote:
> > This observation is not directly to the problem at hand, but it ... - 06:09 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> This observation is not directly to the problem at hand, but it is curious that there isn't ... - 05:34 PM Feature #3814: more schema metadata
- This observation is not directly to the problem at hand, but it is curious that there isn't anything I see about your...
- 05:12 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Please post the original 4GL code and the converted code (not the whole program, just the sn... - 04:58 PM Feature #3814: more schema metadata
- Please post the original 4GL code and the converted code (not the whole program, just the snippets relevant to this q...
- 03:54 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Is the same record being set into the buffer in both calls to @RecordBuffer.setRecord@?
I... - 03:51 PM Feature #3814: more schema metadata
- Is the same record being set into the buffer in both calls to @RecordBuffer.setRecord@?
- 03:43 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Sorry I forgot to respond to this yesterday. Are you sure these code paths are not mutually ... - 03:38 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> Indeed, @RecordBuffer.setRecord@ looks to be a better place. However I've encountered a p... - 03:00 PM Feature #3814: more schema metadata
- @GET-CURRENT@ has an interesting effect on the @_UserTableStat_read@ counter.
* The combination @GET-CURRENT@/@DEL...
04/28/2021
- 12:57 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Code review 3814a rev 12304-12307, part 1.
> *Update*
>
> Does the VST count each indi... - 06:31 AM Feature #3814: more schema metadata
- I've noticed what looks like incompatibility.
In 4GL if inside a transaction block two records are inserted where ...
04/27/2021
- 04:55 PM Feature #3814: more schema metadata
- It looks that if a trigger rejects CREATE/DELETE/FIND/WRITE operation the corresponding @_UserTableStat@ counter is n...
- 12:46 PM Bug #5289: Misc. problems with triggers
- In addition.
The REPLICATION triggers are not invoked in FWD. See the same test as above. Just add the following tr... - 07:20 AM Bug #5289: Misc. problems with triggers
- How to reproduce:
Just run @stat1.p@ with our standard "customer" table and two triggers (see @sftp://<userid>@xfer...
04/26/2021
- 05:14 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Code review 3814a rev 12304-12307, part 2.
>
> *Functional:*
>
> I understand your ter... - 05:01 PM Feature #3814: more schema metadata
- It seems we have enough trigger-related items to warrant a separate issue. Please open a normal priority bug issue in...
- 04:58 PM Feature #3814: more schema metadata
- Code review 3814a rev 12304-12307, part 2.
*Functional:*
I understand your term for persisting the state from t... - 04:56 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> In some situations, the @FIND@ rejected by the trigger causes NPE in the @PreselectQuery@ l... - 04:36 PM Feature #3814: more schema metadata
- In some situations, the @FIND@ rejected by the trigger causes NPE in the @PreselectQuery@ line 5630 (@results@ field ...
- 03:59 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Does the 4GL return @false/no@ from this BUFFER-CREATE method call? If so, then that looks l... - 03:58 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> After rebasing 3814a to 3821c/12334 the trigger is working but contrary to 4GL behavior the... - 03:53 PM Feature #3814: more schema metadata
- Does the 4GL return @false/no@ from this BUFFER-CREATE method call? If so, then that looks like a bug in our create t...
- 03:32 PM Feature #3814: more schema metadata
- After rebasing 3814a to 3821c/12334 the trigger is working but contrary to 4GL behavior the converted @RETURN ERROR@ ...
- 03:13 PM Feature #3814: more schema metadata
- Constantin Asofiei wrote:
> I've tested with 3821c:
> * added the @TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE "cr... - 03:06 PM Feature #3814: more schema metadata
- Constantin Asofiei wrote:
> I've tested with 3821c:
> * added the @TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE "cr... - 03:01 PM Feature #3814: more schema metadata
- I've tested with 3821c:
* added the @TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE "create-trg.p" CRC "30042" @ line ... - 02:51 PM Feature #3814: more schema metadata
- Here is the result of the table conversion:...
- 02:45 PM Feature #3814: more schema metadata
- Constantin Asofiei wrote:
> Please post here the create-trg.p program and the program which tests this trigger.
>
... - 02:42 PM Feature #3814: more schema metadata
- Please post here the create-trg.p program and the program which tests this trigger.
I assume you are *not* running... - 02:41 PM Feature #3814: more schema metadata
- Add the path inside your trigger definition in the @.df@ otherwise it cannot be found in the propath since the propat...
- 02:36 PM Feature #3814: more schema metadata
- Greg Shah wrote:
> OK, so your code should not just be dropped in the root directory of the project. It should be i... - 02:28 PM Feature #3814: more schema metadata
- OK, so your code should not just be dropped in the root directory of the project. It should be in some structured pa...
- 02:24 PM Feature #3814: more schema metadata
- Greg Shah wrote:
> Those are both conversion-time values and they have no meaning at runtime. What project are you ... - 02:22 PM Feature #3814: more schema metadata
- Those are both conversion-time values and they have no meaning at runtime. What project are you using?
- 02:20 PM Feature #3814: more schema metadata
- Constantin Asofiei wrote:
> What is the PROPATH in directory.xml? That one is used at runtime.
>
> Is @create-trg... - 02:11 PM Feature #3814: more schema metadata
- What is the PROPATH in directory.xml? That one is used at runtime.
Is @create-trg.p@ in some folder? If so, add th... - 02:07 PM Feature #3814: more schema metadata
- Greg Shah wrote:
> It must be found in the propath.
Greg.
In my environment the @PROPATH@ is defined in @p2j.cfg... - 01:50 PM Feature #3814: more schema metadata
- It must be found in the propath.
- 01:21 PM Feature #3814: more schema metadata
- I've added a trigger to the test table:...
- 05:13 PM Bug #5289: Misc. problems with triggers
- I've found a number of issues with triggers' support in FWD:
* In 4GL if the @CREATE@ trigger rejects the operation ... - 05:05 PM Bug #5289 (WIP): Misc. problems with triggers
- 05:06 PM Feature #4175 (Closed): add support for -1 (single user) option for CONNECT statement
- I did some additional code cleanup in 3821c/12333. Considering #5279, this issue can be closed.
- 09:04 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> Warning added, functionally looks fine, but please follow coding standards when formatting (... - 08:21 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Code review 3821c/12313:
Warning added, functionally looks fine, but please follow coding standards when formattin...
04/24/2021
- 02:52 PM Bug #3471: incremental conversion is regressed
- 3821c rev 12326 fixes incremental conversion when, in full conversion, the non-new shared temp-table exists in the la...
04/23/2021
- 04:43 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > My implementation is based on the results of the @testcases/... - 04:05 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> My implementation is based on the results of the @testcases/meta/stat1.p@ run. Hopefully,... - 04:39 AM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Code review 3814a rev 12304-12307, part 1.
>
> There are functional, format, and document... - 03:15 PM Bug #5281: BUFFER-COPY does not report changes in some modes
- Adrian Lungu wrote:
> To be fixed: right now I see that setter used inside @RecordBuffer$Handler.invoke()@ can inv... - 03:03 PM Bug #5281: BUFFER-COPY does not report changes in some modes
- When any change is made to a record, @RecordBuffer@ must invoke @reportChange@ to notify registered listeners of the ...
- 02:47 PM Bug #5281 (New): BUFFER-COPY does not report changes in some modes
- 05:53 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Since the @CONNECT@ statement can contain information about multiple databases I've added the log message right where...
- 05:02 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> If we decide to implement this in the future, we will implement with the error 276 as you note. ... - 04:59 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- If we decide to implement this in the future, we will implement with the error 276 as you note. I think that is much...
- 04:48 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> I've been thinking about this task some more. The purpose of this is to enable maintenance progr... - 04:00 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- I've been thinking about this task some more. The purpose of this is to enable maintenance programs to be supported....
04/22/2021
- 06:39 PM Feature #3814: more schema metadata
- Code review 3814a rev 12304-12307, part 1.
There are functional, format, and documentation issues I think we need ... - 08:57 AM Feature #3814: more schema metadata
- Eric: Please review and get this into 3821c unless there is an issue.
- 08:48 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> Eric: Can we close this task?
Greg,
Please remember that the changes are not merged to 3821c ... - 08:33 AM Feature #3814: more schema metadata
- Eric: Can we close this task?
- 07:13 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- I like it. It is conceptually correct.
- 06:32 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > Please note that the "-1" option is supposed to be silently ... - 05:07 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Igor Skornyakov wrote:
> Please note that the "-1" option is supposed to be silently ignored if there is another "... - 04:10 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> Here's a crazy idea which I probably should not be posting at my current level of fatigue, b... - 04:04 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Here's a crazy idea which I probably should not be posting at my current level of fatigue, but here goes...
Can we... - 03:11 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> I don't understand what a proxy for a @Database@ object would do. @Database@ objects are mea... - 03:02 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Igor Skornyakov wrote:
> I also think that full transparency can be achieved easier if the @Database@ (and related o...
04/21/2021
- 06:00 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> > just if no other connections are active?
>
> This one.
I see. Thanks. - 05:58 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- > just if no other connections are active?
This one. - 05:52 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- I also think that full transparency can be achieved easier if the @Database@ (and related objects such as @Persistenc...
- 05:45 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> If at all possible, we should not have differential logic to enforce this limitation for rem... - 05:43 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> > For the local connection - should the "-1" option be considered only for databases that are not... - 05:36 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- If at all possible, we should not have differential logic to enforce this limitation for remote and local databases. ...
- 05:24 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- > For the local connection - should the "-1" option be considered only for databases that are not "loaded at startup"...
- 04:57 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > For the local connection - should the "-1" option be conside... - 04:54 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Igor Skornyakov wrote:
> For the local connection - should the "-1" option be considered only for databases that a... - 04:53 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > Do you mean that database name and user credentials provided... - 04:50 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Igor Skornyakov wrote:
> Do you mean that database name and user credentials provided as @CONNECT@ parameters are ... - 04:47 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> Yes, you are probably right that we should implement it for local and remote databases. Previous... - 04:39 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- > Greg, correct me here if I'm wrong, but I think the limitation needs to be applied whether the connection is remote...
- 03:58 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> The @dbname@ name parameter corresponds with the physical database name configured in the re... - 03:50 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Igor Skornyakov wrote:
> However, I do not understand some details in your explanations.
> Do you mean that in fa... - 03:30 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Eric Faulhaber wrote:
> Igor, as with much of the FWD runtime currently, there is no formal documentation which desc... - 03:18 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Igor, as with much of the FWD runtime currently, there is no formal documentation which describes the internal implem...
- 02:13 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Actually, I do not understand how the current support for @CONNECT@ is supposed to work. Is it documented?
Thank you. - 02:05 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> I don't know exactly, but the @ConnectionManager@ is definitely trying to make a new connection t... - 02:01 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- I don't know exactly, but the @ConnectionManager@ is definitely trying to make a new connection to some remote FWD se...
- 01:50 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- I'm trying to test my support for @CONNECT -1@.
The test program is:... - 08:34 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> We will support this case as I noted above. Forget that FWD is multi-user and focus on meeting t... - 08:27 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- I think you misunderstand. Do NOT assume that we only act as if FWD was a multi-user database server. As I explaine...
- 07:49 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> Good. This is consistent with my previous suggestions. Please go ahead with the implementation.... - 07:40 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> Good. This is consistent with my previous suggestions. Please go ahead with the implementation.... - 07:35 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Good. This is consistent with my previous suggestions. Please go ahead with the implementation.
- 07:31 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> Customers use this to ensure that no other processing is occurring for a database while they are ... - 07:10 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Customers use this to ensure that no other processing is occurring for a database while they are doing some kind of c...
- 07:03 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Sorry, I've started @mpro@ from the directory where the @p2_test.db@ file was located. I cannot connect to the broker...
- 06:55 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Igor Skornyakov wrote:
> Well, if I use @CONNECT -1 -db p2j_test -ld p2j_test1 -U <uid> -P <pwd>.@ while another @mp... - 06:50 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Well, if I use @CONNECT -1 -db p2j_test -ld p2j_test1 -U <uid> -P <pwd>.@ while another @mpro p2j_test@ is running in...
- 06:36 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- That seems inconsistent. How is the @CONNECT@ different from when you tested with the existing multi-user database s...
- 06:30 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> Running the test with an existing mutli-user database server should be sufficient. Go ahead with... - 06:06 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Running the test with an existing mutli-user database server should be sufficient. Go ahead with the implementation.
- 05:56 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> What is the "f" in "fp2j_test.db"?
Sorry, it is a misprint. Should be just @p2j_test.db@ - 05:55 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- What is the "f" in "fp2j_test.db"?
- 05:53 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> > Does it make difference?
>
> Probably not.
>
> Do you see anything inconsistent with my "... - 05:46 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- > Does it make difference?
Probably not.
Do you see anything inconsistent with my "guesses"? Can you implement... - 05:36 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> When you start a @proserve@ multi-user database server for @p2j_test@, what are the results of th... - 05:26 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- > Only one session can be connected to p2_test regardless of how it is done - in the command line or using CONNECT.
... - 04:23 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> If I'm correct, then FWD is like the 2nd scenario. We don't have the command line case. Instead...
04/20/2021
- 06:37 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- If I'm correct, then FWD is like the 2nd scenario. We don't have the command line case. Instead, we have the @CONNE...
- 05:44 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> > After the end I ee (using Database Administrator) two connected databases in both.
>
> What ... - 05:22 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- > After the end I ee (using Database Administrator) two connected databases in both.
What is "ee"?
> The databa... - 04:51 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> I would put a @pause.@ after the @CONNECT@ statements and before the @MESSAGE@ statements. Then ... - 04:40 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Greg Shah wrote:
> Please explain how you run different sessions. The testcase from #4175-6 has no explicit pause, ... - 04:30 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- > Again, everything works fine even in two different sessions.
Please explain how you run different sessions. The... - 03:56 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- Igor Skornyakov wrote:
> At this moment I've run out of ideas. I cannot imagine any reasonable semantics for the "-1... - 03:40 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- I've managed to add two users to the test database and repeated the test described before but using different users f...
- 01:49 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- In addition. For the table database, the "-1" option is mandatory for @CONNECT@ and only a single session can connect...
- 12:45 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- It seems that @CONNECT -1@ is indeed about a single *user*, not a single *session*.
The following test...
04/19/2021
- 03:37 PM Feature #3930 (WIP): allow session level control over the database(s) which are auto-connected
- 02:46 PM Feature #3814: more schema metadata
- Added population of the @_Area@, @_Filelist@, and @_Tenant@ metatables. For the @_Tenant@ only toplevel method and a ...
- 09:38 AM Feature #3814: more schema metadata
- There are multiple applications in consideration here. All 3 tables are used. Our environment should report that it...
- 09:26 AM Feature #3814: more schema metadata
- I see no real usage of @_Filelist@ and @_Tenant@ in the real project I know about. There is a single use of the @_Are...
- 08:56 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> Please finish @_area@, @_filelist@, and @_tenant@.
OK. Thank you. - 08:37 AM Feature #3814: more schema metadata
- Please finish @_area@, @_filelist@, and @_tenant@.
- 08:15 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> > The _area, _filelist and _tenant are not done. I was planning to do it after _usertablestat but... - 08:10 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> Is there a reason we need this in a separate branch?
Eric agreed recently with the separate bran... - 07:38 AM Feature #3814: more schema metadata
- > The _area, _filelist and _tenant are not done. I was planning to do it after _usertablestat but got another assignm...
- 07:36 AM Feature #3814: more schema metadata
- Is there a reason we need this in a separate branch?
> meta database DLLs
Dynamic Link Libraries? What is DLL ... - 06:00 AM Feature #3814: more schema metadata
- A "smoke test" of the large customer app passed OK with 3814a and manually updated meta database DDLs (@_MyConnect@ c...
- 05:43 AM Feature #3814: more schema metadata
- @_UserTableStat@ support is finished. At least now @testcases/meta/stat1.p@ produces the same results both in 4GL and...
- 03:55 AM Feature #3814: more schema metadata
- Good news.
Contrary to my initial assumptions based on an incorrect interpretation of the early test results, @_Us...
04/15/2021
- 03:16 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> If you think (a) you are not close to finished with the changes; or (b) they are especially ... - 03:01 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> BTW: I already have a lot of uncommitted changes for the 3821c. Maybe it makes sense to c... - 07:23 AM Feature #3814: more schema metadata
- The problem with @InterruptedException@ is resolved. See attached .diff file.
The reason was the following. @UserT... - 03:45 AM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Please see #3896. We need to make much more substantial changes to the implementation suppor... - 08:08 AM Bug #3896: improve performance of the _lock metadata implementation
- Greg Shah wrote:
> This approach should be generalized. I think there are many other tables that would be better im... - 07:49 AM Bug #3896: improve performance of the _lock metadata implementation
- This approach should be generalized. I think there are many other tables that would be better implemented this way.
- 07:38 AM Bug #3896: improve performance of the _lock metadata implementation
- Greg Shah wrote:
> I don't think this is a radical idea. It is exactly what I've been suggesting for years. See #3... - 07:31 AM Bug #3896: improve performance of the _lock metadata implementation
- I don't think this is a radical idea. It is exactly what I've been suggesting for years. See #3896-3.
- 03:39 AM Bug #3896: improve performance of the _lock metadata implementation
- Maybe it makes sense to implement the @_Lock@ support in the same way it is done for the @_UserTableStat@? I mean ke...
04/14/2021
- 06:03 PM Feature #3814: more schema metadata
- Please see #3896. We need to make much more substantial changes to the implementation supporting @_Lock@ metadata, th...
- 05:16 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> One more difference between the two tests.
> With @stat.p@ I see a normal decorated window... - 04:45 PM Feature #3814: more schema metadata
- One more difference between the two tests.
With @stat.p@ I see a normal decorated window from the very beginning. Wi... - 04:21 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> I've noticed a strange thing. As I wrote before, I have two tests @stat.p@ and @stat1.p@. I... - 04:13 PM Feature #3814: more schema metadata
- I've noticed a strange thing. As I wrote before, I have two tests @stat.p@ and @stat1.p@. I convert both of them.
If... - 02:59 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> To the degree a metadata table is writable and is updated from converted application logic, ... - 02:33 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> More about the issue with @InterruptedExcception@.
> I have two tests in @testcases/meta@:... - 02:04 PM Feature #3814: more schema metadata
- More about the issue with @InterruptedExcception@.
I have two tests in @testcases/meta@: @stat.p@ and @stat1.p@. I s... - 07:50 AM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> Sometimes I get the following exception:
> [...]
> I've never seen that before. Please no... - 07:18 AM Feature #3814: more schema metadata
- Sometimes I get the following exception:...
04/13/2021
- 04:48 PM Feature #3814: more schema metadata
- Ovidiu Maxiniuc wrote:
> BTW, to see what exactly there is stored in a table at a given moment you can put a breakpo... - 04:33 PM Feature #3814: more schema metadata
- BTW, to see what exactly there is stored in a table at a given moment you can put a breakpoint in your IDE and execut...
- 04:33 PM Feature #3814: more schema metadata
- Ovidiu Maxiniuc wrote:
> I did a quick conversion and run your testcase with @show_sql=true@ for persistent database... - 04:29 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Without debugging, I do not know. What does the program do in FWD? Are you seeing the error ... - 04:27 PM Feature #3814: more schema metadata
- I did a quick conversion and run your testcase with @show_sql=true@ for persistent database in my @directory.xml@.
H... - 04:25 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> I'm running the following test program:
> [...]
>
> With 4GL I see 1 creates, 5 reads, ... - 04:13 PM Feature #3814: more schema metadata
- Without debugging, I do not know. What does the program do in FWD? Are you seeing the error message after the @BUFFER...
- 03:30 PM Feature #3814: more schema metadata
- I'm running the following test program:...
- 01:32 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> See @UserTableStatUpdater.updateRecord@ at line 225:
>
> [...]
>
> This file needs a f... - 01:28 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> I've tested my (not yet committed) changes with a large customer app.
> I've noticed a pro... - 01:22 PM Feature #3814: more schema metadata
- I've tested my (not yet committed) changes with a large customer app.
I've noticed a problem with @_UserTableStat@ o...
04/12/2021
- 09:12 AM Feature #4176: make certain metadata tables aware of live runtime state
- How much of this task is already complete from the work done in #3814?
- 06:40 AM Feature #3813 (Closed): misc DB features part deux
- 05:40 AM Feature #3813: misc DB features part deux
- The @BUFFER-FIELD:DECIMALS@ support looks correct with 3821c/12264.
04/09/2021
- 12:05 PM Feature #3814: more schema metadata
- I am ok with disabling the caching for metadata tables, for the reasons already discussed above. If we find some perf...
- 07:20 AM Feature #3814: more schema metadata
- Added additional configuration options for the 'remote-meta' mode to simplify the development/debugging of the metada...
- 07:15 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> Eric will respond more fully to your concerns. But one thing I can point out here is that the co... - 07:00 AM Feature #3814: more schema metadata
- Eric will respond more fully to your concerns. But one thing I can point out here is that the converted 4GL code is ...
- 06:15 AM Feature #3814: more schema metadata
- In addition to a previous note.
In contrast with the situation with customer tables (both primary and temporary), ...
04/08/2021
- 05:18 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > I do not think that it makes much sense to use cache with me... - 04:22 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> I do not think that it makes much sense to use cache with metatables, at least for reques... - 01:19 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Yes, we probably don't have invalidation logic for places where we update/insert/delete meta... - 12:42 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> I've disabled the @RandomAccessQuery.ffCache@ usage for meta tables and now @MyConnction@... - 10:59 AM Feature #3814: more schema metadata
- The @_MyConnection@ support is fixed (see however #3814-315).
Please review the changes vs. 3821c/12259.
Thank yo... - 07:54 AM Feature #3814: more schema metadata
- Committed trigger function for @meta_myconnection@ view to 3821c/12258. It doesn't have any effect until other change...
- 06:33 AM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> The cache logic in the @RandomAccessQuery.execute()@ seems to be not 100% correct. For @_My... - 06:17 AM Feature #3814: more schema metadata
- The cache logic in the @RandomAccessQuery.execute()@ seems to be not 100% correct. For @_MyConnection@ it finds the @...
- 04:49 AM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> As I wrote, H2 seems not to understand a UDF definition that I've provided. This means that...
04/07/2021
- 05:22 PM Feature #3814: more schema metadata
- > I think the UDF definition is correct, but please remove the @session_id@ column and the use of the UDF in the @cre...
- 05:00 PM Feature #3814: more schema metadata
- I think the UDF definition is correct, but please remove the @session_id@ column and the use of the UDF in the @creat...
- 03:34 PM Feature #3814: more schema metadata
- I've created a function...
- 03:20 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> The context-local @_MyConn-Id@ will have to be the same value across connected, primary data... - 02:50 PM Feature #3814: more schema metadata
- There is no physically separate "server-side" in this case. The @_meta@ database is an embedded, in-memory database, ...
- 02:08 PM Feature #3814: more schema metadata
- Unfortunately, the trick with view/trigger doesn't for the same reason which complicated the approach bases on the te...
- 01:43 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Sorry, I'm not following... do you mean the FWD runtime code, or the converted business logi... - 01:40 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> It seems like the view could be filtered on @_MyConn-Id@, rather than introducing another un... - 01:30 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> The reason is to avoid *any* changes in the Java code. All we need is a new trigger class... - 01:24 PM Feature #3814: more schema metadata
- Another question...isn't...
- 01:21 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> I'm not sure why the trigger would be needed in this case. The @_Myconnection@ VST is read-o... - 01:15 PM Feature #3814: more schema metadata
- I'm not sure why the trigger would be needed in this case. The @_Myconnection@ VST is read-only for general use. The ...
- 11:51 AM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Please illustrate this idea further. I have not used INSTEAD OF triggers, but I understand s... - 11:46 AM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> If we create a corresponding INSTEAD OF triggers for the view, then only changes in the D... - 10:58 AM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> Igor Skornyakov wrote:
> > I suggested adding an additional condition to all SELECTs from ... - 10:42 AM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> I suggested adding an additional condition to all SELECTs from @_MyConnection@ so that only... - 09:56 AM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> I am not suggesting any change to your planned support for the @_UserTableStat@ table. But f... - 09:44 AM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> I understand that using a local temporary table for the @_UserTableStat@ requires a separat... - 05:47 AM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> Eric Faulhaber wrote:
> > Sorry, I should have used the term temporary table, so as not to...
04/02/2021
- 02:21 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Sorry, I should have used the term temporary table, so as not to confuse with temp-table, wh... - 02:20 PM Feature #3814: more schema metadata
- Sorry, I should have used the term temporary table, so as not to confuse with temp-table, which is the 4GL term.
T... - 01:58 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> It seems to me this can be driven primarily from the @ConnectionManager@. Where are the ma... - 01:49 PM Feature #3814: more schema metadata
- I've finished with persisting of the @_UserTableStat@ data and update of the @_UserTableStat._UserTableStat-read@ cou...
- 01:47 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> Your suggestion with temp tables looks cleaner than mine but seems to be more complicated... - 12:56 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> I do think we need to work on correcting the @_myconnection@ implementation sooner rather th... - 12:25 PM Feature #3814: more schema metadata
- I do think we need to work on correcting the @_myconnection@ implementation sooner rather than later.
The implemen... - 03:35 AM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Greg, is right, we did not implement the @_myconnection@ table correctly. For each context/s... - 12:48 AM Feature #3814: more schema metadata
- Greg, is right, we did not implement the @_myconnection@ table correctly. For each context/session, there should only...
Also available in: Atom