Activity
From 04/01/2020 to 04/30/2020
04/30/2020
- 06:56 PM Feature #4011: database/persistence layer performance improvements
- Constantin Asofiei wrote:
> For persistent procedures, a buffer will live as long as that program lives.
Hm, ri... - 06:24 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> Specifically, I provisionally have decided on the approach where we tie the database session... - 05:55 PM Feature #4011: database/persistence layer performance improvements
- Constantin, I need some guidance on my previous entry.
Specifically, I provisionally have decided on the approach ... - 03:50 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> If @Persistence.closeSession(false)@ is called only from @Persistence$Context.cleanup()@. T... - 10:08 AM Feature #4011: database/persistence layer performance improvements
- I agree that refactoring and using modules are both very good things. And we are definitely wanting to do some of th...
- 09:34 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> When we upgrade to Java9 we could make use of the new modules and compile them independentl... - 09:24 AM Feature #4011: database/persistence layer performance improvements
- Greg Shah wrote:
> In #4155 we are working to eliminate use of the @.df@. And converting as part of the build proce... - 09:10 AM Feature #4011: database/persistence layer performance improvements
- Greg Shah wrote:
> In #4155 we are working to eliminate use of the @.df@. And converting as part of the build proce... - 08:58 AM Feature #4011: database/persistence layer performance improvements
- In #4155 we are working to eliminate use of the @.df@. And converting as part of the build process leads to a bootst...
- 08:50 AM Feature #4011: database/persistence layer performance improvements
- Greg Shah wrote:
> > taking in consideration that we do not have the class at the moment FWD is compiled
>
> In m... - 08:44 AM Feature #4011: database/persistence layer performance improvements
- > taking in consideration that we do not have the class at the moment FWD is compiled
In my opinion, it makes no s...
04/29/2020
- 05:29 PM Feature #4011: database/persistence layer performance improvements
- Last night I committed r11422.
This revision re-enables @LockTableUpdater@, @ConnectTableUpdater@ and @TransactionT... - 04:09 PM Feature #4011: database/persistence layer performance improvements
- If @Persistence.closeSession(false)@ is called only from @Persistence$Context.cleanup()@. This is the end of session,...
- 02:33 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> Just committed r11421.
> There are two changes:
> # in @Persistence.closeSession(boolean)... - 06:32 AM Feature #4011: database/persistence layer performance improvements
- For now, don't change what the queries fetch. If a query fetches all columns, leave it that way, but ensure the prima...
- 08:47 PM Feature #4011: database/persistence layer performance improvements
- I observed the following usecase:
* some records are created fresh in a loop and get saved. They are successfully in...
04/28/2020
- 04:20 PM Feature #4011: database/persistence layer performance improvements
- Just committed r11421.
There are two changes:
# in @Persistence.closeSession(boolean)@, the @closeSessionImpl(error... - 01:36 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> Briefly speaking, the problem is caused because the static temp-tables are 'permanent', a... - 11:50 AM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> One more issue to fix is that it seems we are not properly dropping indexes on temporary tab... - 08:18 AM Feature #4011: database/persistence layer performance improvements
- > At each nested block within that application transaction, the SavepointManager sets a database savepoint. If that b...
- 05:51 AM Feature #4011: database/persistence layer performance improvements
- One more issue to fix is that it seems we are not properly dropping indexes on temporary tables upon exiting Hotel GU...
- 05:32 AM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> For undoable DMOs marked stale, the next access forces a re-read of that DMO's data from t... - 05:25 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> I think there is an issue with the nesting transactions. [...]
I debugged through this... - 04:20 AM Feature #4011: database/persistence layer performance improvements
- Thanks for clarifications, I will use these information (from both your last posts) to continue investigations on the...
- 03:37 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> Eric Faulhaber wrote:
> > I don't intentionally create nested transactions, in fact, the @... - 03:09 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> Eric Faulhaber wrote:
> > Can you please share the reasoning behind your change?
> The ... - 09:10 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> I don't intentionally create nested transactions, in fact, the @inTx@ flag in @Session@ is i... - 09:03 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> Can you please share the reasoning behind your change?
The usecase is when same dmo is load... - 08:50 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu, the change in 11418 to @Session.save@ seems dangerous to me. The reason for the check to test whether another...
- 12:16 PM Feature #4397: add database attrs, methods and options
- Greg Shah wrote:
> The runtime would be up to Eric/Ovidiu. After #4011, they have plenty of control all the way dow... - 10:08 AM Feature #4397: add database attrs, methods and options
- 4231b rev 11493 :
* added BUFFER:LAST-BUFFER and QUERY's callback API support
* fixed EXCEPT/FIELDS option with a r... - 09:43 AM Feature #4397: add database attrs, methods and options
- Looks like FIELDS and EXCEPT are already supported for this case:...
- 09:41 AM Feature #4397: add database attrs, methods and options
- The runtime would be up to Eric/Ovidiu. After #4011, they have plenty of control all the way down to the JDBC driver.
- 09:24 AM Feature #4397: add database attrs, methods and options
- I understand the reasoning behind it, to limit the amount of data retrieved by a query; but, my point is that to make...
- 09:15 AM Feature #4397: add database attrs, methods and options
- Constantin Asofiei wrote:
> I recall way back that we had a talk about FIELDS/EXCEPT with a record phrase, and with ... - 08:16 AM Feature #4397: add database attrs, methods and options
- Yes, it exists:...
- 08:12 AM Feature #4397: add database attrs, methods and options
- Constantin Asofiei wrote:
> > Where did you find from of the existence of the attribute for dataset objects? Custome... - 07:32 AM Feature #4397: add database attrs, methods and options
- Ovidiu Maxiniuc wrote:
> Constantin Asofiei wrote:
> > Just a note, there is a @DATASET:FILL-MODE@ attribute which ... - 07:01 AM Feature #4397: add database attrs, methods and options
- Constantin Asofiei wrote:
> Just a note, there is a @DATASET:FILL-MODE@ attribute which I stubbed in 4231b. FWD now... - 10:16 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> > Why not keep the metadata in the database as 4GL does?
>
> Just because the 4GL represents t... - 10:08 AM Feature #3814: more schema metadata
- > Why not keep the metadata in the database as 4GL does?
Just because the 4GL represents these as tables, doesn't ... - 09:49 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> When you add a column or an index post-conversion, it must be represented in the metadata. Relyi... - 08:00 AM Feature #3814: more schema metadata
- When you add a column or an index post-conversion, it must be represented in the metadata. Relying upon static defin...
04/27/2020
- 07:20 PM Feature #3814: more schema metadata
- Greg Shah wrote:
> At least for tables such as @file_@ or @field_@, these must always represent the latest structu... - 06:47 PM Feature #3814: more schema metadata
- Greg Shah wrote:
> > I can easily imagine the situation when we'll be able to provide compatibility with 4GL for the... - 06:35 PM Feature #3814: more schema metadata
- > I can easily imagine the situation when we'll be able to provide compatibility with 4GL for the application if we w...
- 06:00 PM Feature #3814: more schema metadata
- Greg Shah wrote:
> > I've not realized this. In any case, the content of the non-VST system tables should be really ... - 05:45 PM Feature #3814: more schema metadata
- > I've not realized this. In any case, the content of the non-VST system tables should be really persistent and survi...
- 05:25 PM Feature #3814: more schema metadata
- Constantin Asofiei wrote:
> Igor, AFAIK the meta database in FWD is a separate H2 in-memory database, for each physi... - 05:20 PM Feature #3814: more schema metadata
- Igor, AFAIK the meta database in FWD is a separate H2 in-memory database, for each physical database. So even if the...
- 04:31 PM Feature #3814: more schema metadata
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
> > Well, it seems that we need some changes in the conversion proce... - 04:20 PM Feature #3814: more schema metadata
- Igor Skornyakov wrote:
> Well, it seems that we need some changes in the conversion process. The SCHEMA meta tables ... - 06:44 PM Feature #4397: add database attrs, methods and options
- I recall way back that we had a talk about FIELDS/EXCEPT with a record phrase, and with our current FWD, it doesn't m...
- 06:39 PM Feature #4397: add database attrs, methods and options
- Just a note, there is a @DATASET:FILL-MODE@ attribute which I stubbed in 4231b. FWD now has runtime only for @BUFFER...
- 05:37 PM Feature #4011: database/persistence layer performance improvements
- I don't intentionally create nested transactions, in fact, the @inTx@ flag in @Session@ is intended specifically to a...
- 05:24 PM Feature #4011: database/persistence layer performance improvements
- Eric,
I committed a small update that will make the embedded client work. See r11418.
But I have the following is... - 03:45 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> [...]
> This was making sense when we let Hibernate do the flush as late as possible, bu... - 08:47 AM Feature #4011: database/persistence layer performance improvements
- Eric,
We need to discuss the ... - 06:05 AM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> This is fixed in rev 11417.
Super!
> Ovidiu, after the issues in #4011-241, could you al... - 06:00 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu, after the issues in #4011-241, could you also please take a look at what is going wrong with embedded mode Ho...
- 05:48 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> Eric Faulhaber wrote:
> > What is the recreate for this? I can have a look.
> Available R... - 02:15 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu, thanks for the fixes in rev 11416. Please look at these next, which occur when you try to manipulate the tree...
04/25/2020
- 02:48 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> I've now come across a dynamic database problem in Hotel GUI (virtual desktop). On the "Room... - 02:37 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> What is the recreate for this? I can have a look.
Available Rooms > Check-In > (select a gu... - 02:34 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> The issue I was after yesterday changes a bit. [...]
What is the recreate for this? I ... - 11:28 AM Feature #4011: database/persistence layer performance improvements
- Eric,
The issue I was after yesterday changes a bit. Now I am getting the following NPE when a record is deleted:
<... - 09:01 AM Feature #4011: database/persistence layer performance improvements
- > The problem with my last revision is that I was assuming Finalizable entry and finished calls were always paired, w...
- 04:19 AM Feature #4011: database/persistence layer performance improvements
- I've committed rev 11415, which I believe fixes the @UniqueTracker@ scope imbalance problem. I think the logic is sou...
04/24/2020
- 04:11 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> the first part, @on commit drop@ means to drop the table on transaction commit. Now, I do... - 10:07 AM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> Why do we create temp tables with the postfix @on commit drop transactional@? What does this... - 04:23 AM Feature #4011: database/persistence layer performance improvements
- Update on the unbalanced scopes in @UniqueTracker@...
I've reworked the scope mechanism in @UniqueTracker@ to rely... - 02:19 PM Feature #4375: add support for -pf <profile_filename> option for CONNECT statement
- Greg Shah wrote:
> It looks like rev 11369 of 4231b.
>
> As you develop changes for a task, please keep the @% Do... - 01:29 PM Feature #4375 (Test): add support for -pf <profile_filename> option for CONNECT statement
- It looks like rev 11369 of 4231b.
As you develop changes for a task, please keep the @% Done@ and @Status@ updated... - 01:13 PM Feature #4375: add support for -pf <profile_filename> option for CONNECT statement
- Greg Shah wrote:
> Are the changes in 4231b?
I do not remember. I think that they are in the trunk already. - 01:12 PM Feature #4375: add support for -pf <profile_filename> option for CONNECT statement
- Are the changes in 4231b?
- 01:11 PM Feature #4375: add support for -pf <profile_filename> option for CONNECT statement
- This was done in the scope of #3813.
- 11:46 AM Feature #4375: add support for -pf <profile_filename> option for CONNECT statement
- I think I mistakenly assigned you #4392 previously, but meant for you to work this one.
- 01:06 PM Feature #4175: add support for -1 (single user) option for CONNECT statement
- I was not working in this task/ As far as I remember, I was reassigned to another one.
- 11:44 AM Feature #4175: add support for -1 (single user) option for CONNECT statement
- What is the status of this task?
04/23/2020
- 04:58 PM Feature #4011: database/persistence layer performance improvements
- Why do we create temp tables with the postfix @on commit drop transactional@? What does this do?
- 03:49 PM Feature #4011: database/persistence layer performance improvements
- I just committed r11414. Here are the changes:
* changed the initialization of @_metadata@ of @DmoClass@ generated c... - 02:33 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> Do we need to be so eager to close the session in the attempt to salvage the normal execu... - 10:44 AM Feature #4011: database/persistence layer performance improvements
- I used r11413 and the hotel_gui has @deploy.all@-ed smoothly. I found some new hardcoded @id@ which were replaced wit...
- 08:15 AM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> I was not thinking of database import when I put @PRIMARY_KEY_NAME@ into @DatabaseManager@. ... - 06:10 AM Feature #4011: database/persistence layer performance improvements
- The attached changes to @directory.xml@ are needed to adjust for the removal of Hibernate. Note that these are just t...
- 06:02 AM Feature #4011: database/persistence layer performance improvements
- I checked in rev 11413, which fixes a few bugs (hard-coded references to @id@ as primary key) and makes @Session.PK@ ...
- 04:44 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> * the @DatabaseManager.PRIMARY_KEY@ is used when initializing the @DmoMeta@ for each DMO ... - 09:33 AM Bug #3471: incremental conversion is regressed
- 4231b rev -11481- 11482 contains more performance fixes (again, related to the @tmpTabNodes@ and @AstKey@):
* collec...
04/22/2020
- 03:31 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> Is @MultiClassLoader@ really needed for the import, or just @AsmClassLoader@?
Good point.... - 03:24 PM Feature #4011: database/persistence layer performance improvements
- Is @MultiClassLoader@ really needed for the import, or just @AsmClassLoader@?
- 03:21 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> BTW, for import and server to start the
> @-Djava.system.class.loader=com.goldencode.p2... - 03:20 PM Feature #4011: database/persistence layer performance improvements
- BTW, for import and server to start the
@-Djava.system.class.loader=com.goldencode.p2j.classloader.MultiClassLoad... - 03:06 PM Feature #4011: database/persistence layer performance improvements
- Eric,
I committed r11412. The changes include:
* I fixed the reported issue. It was caused by the @key@ being dif... - 05:20 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu, when I try to log into Hotel GUI embedded mode (or run any test case) with rev 14111, I get this:...
- 08:18 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
>> I noticed your TODO in DatabaseManager. I am going to address is immediately as this is use...
04/21/2020
- 08:07 AM Feature #3814: more schema metadata
- At this moment I'm using the current approach based on @metadata@ in @p2j.cfg.xml@. I believe that it will be easy to...
- 08:02 AM Feature #3814: more schema metadata
- We can leave behind a conversion artifact for this, since the dynamic queries are only processed at runtime this shou...
- 03:47 AM Feature #3814: more schema metadata
- Greg/Igor: a VST can be used from dynamic queries, too. And this will leave nothing for us to determine via the stan...
- 06:08 AM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> I merged in my changes related to import and a few other fixes. Latest revision of 4011a is... - 10:01 PM Feature #4011: database/persistence layer performance improvements
- I merged in my changes related to import and a few other fixes. Latest revision of 4011a is 11411. Notes:
* the prop...
04/20/2020
- 08:42 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> > I do not understand what the "conversion support" (#3814-7) means as it seems that it is suffic... - 08:29 AM Feature #3814: more schema metadata
- > I do not understand what the "conversion support" (#3814-7) means as it seems that it is sufficient just to add the...
- 07:52 AM Feature #3814: more schema metadata
- Looking at the content of the @_Database-Feature@ VST from the sample customer environment I do not think that it can...
- 05:17 AM Feature #4011: database/persistence layer performance improvements
- I committed rev 11409. With this drop, I can log into virtual desktop Hotel GUI. I can navigate the tabs, though the ...
- 03:34 AM Feature #4011: database/persistence layer performance improvements
- I've checked in revisions 11407 and 11408, which replace the UNDO architecture and the transaction management.
Ple...
04/19/2020
- 02:39 PM Feature #3814: more schema metadata
- Well, it seems that we need some changes in the conversion process. The SCHEMA meta tables should be included in the ...
- 12:48 PM Feature #3814: more schema metadata
- In this note, I summarise my current understanding of the scope of this task and things which are not clear for me.
...
04/18/2020
- 08:58 AM Feature #3814: more schema metadata
- Greg Shah wrote:
> You've been analyzing this for a few days. Please provide more details so we can discuss.
Gre... - 07:06 AM Feature #3814: more schema metadata
- > I understand that most of the data mentioned in this task are related to data security.
I don't think so. The @...
04/17/2020
- 02:28 PM Feature #3814: more schema metadata
- I understand that most of the data mentioned in this task are related to data security. I'm not sure that most of the...
04/16/2020
- 04:21 PM Bug #3471: incremental conversion is regressed
- 4231b rev 11462 contains some performance fixes related to the memory usage.
The idea here was:
* 'unpin' the AST... - 04:03 PM Bug #3471: incremental conversion is regressed
- Additional notes which may be useful:
The core idea is that the FWD ConversionDriver has an incremental conversion... - 12:05 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Igor: Can you please commit your import fixes so that the build is working again? I need to push... - 11:24 AM Feature #3813: misc DB features part deux
- Igor: Can you please commit your import fixes so that the build is working again? I need to push this to our customers.
04/15/2020
- 07:15 PM Feature #3813: misc DB features part deux
- Constantin Asofiei wrote:
> Igor, there is an issue in @BufferFieldImpl@ - this import "import org.aspectj.org.eclip... - 06:29 PM Feature #3813: misc DB features part deux
- Igor, there is an issue in @BufferFieldImpl@ - this import "import org.aspectj.org.eclipse.jdt.core.dom.*;" is not OK...
- 07:11 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> However, I have another question on this topic: aren't the values in each row of the @.d@ fi... - 07:05 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> [...] I think we can either:
> * drop the method, I think the association property-index c... - 06:52 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> The other issue is that I had removed the deprecated @BaseRecord.indexOf@ method in my worki... - 06:01 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> I found out that @PropertyMapper@ tries to delegate the setting of a field if @delegate@ ... - 05:12 PM Feature #4011: database/persistence layer performance improvements
- Eric,
I started rewriting some parts of the @import.xml@, @ImportWorker@ and related classes to take advantage of th... - 09:46 AM Bug #3471 (Closed): incremental conversion is regressed
- 09:15 PM Feature #4613: add missing support for database user defined functions (UDF) if they are supporte...
- FWD supports many built-in functions for use in WHERE clauses, such that they are executed at the database server usi...
04/14/2020
- 07:03 PM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> Igor, I will open a new task for this. We will need to put together a process for identifyin... - 06:54 PM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> The only remaining thing in this task is @Built-In Function Usage in WHERE Clauses@.
> Whe... - 03:33 PM Feature #3813: misc DB features part deux
- The only remaining thing in this task is @Built-In Function Usage in WHERE Clauses@.
Where can I take a look at the ... - 03:30 PM Feature #3813: misc DB features part deux
- Implemented runtime support for the @BUFFER:BUFFER-VALIDATE@.
4231b revision 11447. - 06:58 PM Feature #4613 (New): add missing support for database user defined functions (UDF) if they are su...
- 06:06 PM Bug #3471: incremental conversion is regressed
- Branch 3471a was merged to trunk rev 11346 and archived. This adds support for incremental conversion. Not mandator...
- 05:43 PM Bug #3471: incremental conversion is regressed
- Phase 2 planning:
* move the h2-related code as a service in goldencode.ast
* tmpTabNodes usage - find a better way... - 11:58 AM Bug #3471: incremental conversion is regressed
- Code Review Task Branch 3471a Revision 11376
I'm fine with the changes. You can merge to trunk when your testing ... - 11:27 AM Bug #3471: incremental conversion is regressed
- The lambda issues were addressed in 3471a 11375.
I think this can be merged to trunk, after I finish another conve... - 11:15 AM Bug #3471: incremental conversion is regressed
- 3471a rev 11376 contains a fix for #4384-187 issue related to converting references for builtin classes with no FWD i...
- 04:57 PM Feature #3814: more schema metadata
- Ovidiu Maxiniuc wrote:
> Igor, you can query the meta tables from a 4GL environment as a standard stable. For exampl... - 04:35 PM Feature #3814: more schema metadata
- Igor, you can query the meta tables from a 4GL environment as a standard stable. For example:...
- 04:13 PM Feature #3814: more schema metadata
- Where can I find the description of the schema metadata? So far I've found only this article: https://knowledgebase.p...
04/13/2020
- 07:02 PM Bug #3471: incremental conversion is regressed
- Greg Shah wrote:
> 5. The design is quite elegant. The fact that the maps and sets in conversion have been replaced... - 06:54 PM Bug #3471: incremental conversion is regressed
- Code Review Task Branch 3471a Revision 11373
+Part 2+
5. The design is quite elegant. The fact that the maps a... - 06:33 PM Bug #3471: incremental conversion is regressed
- Greg Shah wrote:
> 1. In the calling locations of @helper.persistCollection()@ it would be better if the types of t... - 04:34 PM Bug #3471: incremental conversion is regressed
- Code Review Task Branch 3471a Revision 11373
So far, I've very impressed.
+Part 1+
I'm posting the review in... - 07:27 AM Bug #3471: incremental conversion is regressed
- Greg, 3471a rev 11373 is ready for review
- 09:11 AM Feature #3813: misc DB features part deux
- Implemented changes suggested by Eric (see #3813-157) and fixed dependency of the DMO instantiation on @SESSION:DATE...
- 05:26 AM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> No, please don't work on the conversion part. The @LegacyField@ annotation is precisely the ... - 05:05 AM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> Greg Shah wrote:
> > Igor: Can you implement the parts of the support except for the looku... - 05:03 AM Feature #3813: misc DB features part deux
- Igor, for @LegacyField@ look in @dmo_common.rules@, around line 1780, for code like this:...
- 03:24 AM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Igor: Can you implement the parts of the support except for the lookup of the value? Then it can... - 09:20 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Eric: I assume you mean that just the backing value is there in the DMO in 4011a. The rest of th...
04/12/2020
- 07:40 PM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > I'm supposed to work at least on @DECIMALS@ support right no... - 05:05 PM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> The other issue is that I had removed the deprecated @BaseRecord.indexOf@ method in my worki... - 05:03 PM Feature #4011: database/persistence layer performance improvements
- Thanks for fixing up the import.
I had two errors compiling with rev 11406. One was due to a change I have made in...
04/11/2020
- 04:12 PM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> Sorry, Igor, would not have been giving you implementation advice had I realized Ovidiu alre... - 04:08 PM Feature #3813: misc DB features part deux
- Sorry, Igor, would not have been giving you implementation advice had I realized Ovidiu already implemented this feat...
- 04:01 PM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> I'm supposed to work at least on @DECIMALS@ support right now.
If there is not a criti... - 03:58 PM Feature #3813: misc DB features part deux
- Ovidiu Maxiniuc wrote:
> [...]
> Both attributes and can be directly accessed via the new @DmoMetadataManager@ / @D... - 03:03 PM Feature #3813: misc DB features part deux
- Ovidiu Maxiniuc wrote:
> Igor, I believe both of the above attributes are members fields in the new @Property@ DMO a... - 02:50 PM Feature #3813: misc DB features part deux
- Igor, I believe both of the above attributes are members fields in the new @Property@ DMO annotation of the new persi...
- 08:08 AM Feature #3813: misc DB features part deux
- Can anybody help me to understand how the @LegacyField@ annotations are generated? We need at least two fixes for thi...
04/10/2020
- 06:06 PM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > I need the get the @DECIMALS@ value from the @BufferFieldImp... - 06:00 PM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> I need the get the @DECIMALS@ value from the @BufferFieldImpl@ method I do not see how ge... - 04:38 PM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> The DMO field will always return a BDT value, never @null@, even if it is unknown value. The... - 03:58 PM Feature #3813: misc DB features part deux
- Fixed the issue with @INITIAL@ value parsing for date fields.
Committed with @SessionExport@ support to 4231b revis... - 03:06 PM Feature #3813: misc DB features part deux
- I've removed my changes regarding @LogicalTerminal@. Apart from extracting @SessionExports@ operations to a separate ...
- 01:57 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> > I understand that EnvironmentDaemon is not a suitable pattern for the situation with SESSION:DA... - 01:46 PM Feature #3813: misc DB features part deux
- > I understand that EnvironmentDaemon is not a suitable pattern for the situation with SESSION:DATE-FORMAT and the ot...
- 01:11 PM Feature #3813: misc DB features part deux
- I understand that @EnvironmentDaemon@ is not a suitable pattern for the situation with @SESSION:DATE-FORMAT@ and the ...
- 04:26 PM Feature #4011: database/persistence layer performance improvements
- The first revision of import process was committed to 4011a. I have successfully imported the hotel_gui database in b...
04/09/2020
- 03:32 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Yes, it will certinly make it better, even if it is not the full solution.
>
> You can patte... - 03:30 PM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> BTW: maybe the problem is not with the @SessionUtils@ _per se_, but in the way @SessionExpo... - 03:29 PM Feature #3813: misc DB features part deux
- Yes, it will certinly make it better, even if it is not the full solution.
You can pattern it using the @Environ... - 03:29 PM Feature #3813: misc DB features part deux
- BTW: maybe the problem is not with the @SessionUtils@ _per se_, but in the way @SessionExports@ is instantiated in th...
- 02:55 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Yes. This is what I meant by my comment:
>
> > I don't know why we are using SessionUtils on ... - 02:47 PM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> A @SESSION:TIMEZONE = 3.@ (@SessionUtils.setTimezone@) causes the same exception as in #381... - 02:45 PM Feature #3813: misc DB features part deux
- A @SESSION:TIMEZONE = 3.@ (@SessionUtils.setTimezone@) causes the same exception as in #3813-123 (@No export or no ac...
04/07/2020
- 05:19 PM Feature #4011: database/persistence layer performance improvements
- While working with the @hotel_gui@ and in particular with embedded client I feel that FWD is non-deterministically un...
- 04:46 PM Feature #3813: misc DB features part deux
- The runtime support for the @DEFAULT-STRING@ (modulo the issue with EXTENT fields (see #3813-99) is finished.
Commit... - 04:27 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Most likely, the initial value for these problem cases should be the unknown value. Please check... - 04:24 PM Feature #3813: misc DB features part deux
- > I've implemented preventive pre-check in the getDefaultString and do not try to vet the values for the problematic ...
- 04:01 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> > Formally this issue is not related to #3813 and does not prevent tesing.
>
> We still should... - 03:59 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> > I've found that current INITIAL attribute support generates exceptions for other data types (su... - 03:48 PM Feature #3813: misc DB features part deux
- > Formally this issue is not related to #3813 and does not prevent tesing.
We still should probably fix this now. ... - 03:37 PM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Igor Skornyakov wrote:
> > On the conversion of the field definition
> > [...]
> > the time pa... - 03:31 PM Feature #3813: misc DB features part deux
- Another issue:
The converted statement @SessionUtils.setDateFormat(new character("ydm"))@ causes runtime exception:
... - 03:30 PM Feature #3813: misc DB features part deux
- > I've found that current INITIAL attribute support generates exceptions for other data types (such as raw or even ch...
- 03:27 PM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> On the conversion of the field definition
> [...]
> the time part is lost.
Please show... - 03:23 PM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> I don't think that was intentional. Please add it if you need it. My advice about @getPrecis... - 03:21 PM Feature #3813: misc DB features part deux
- In addition to the #3813-95, I've found that current @INITIAL@ attribute support generates exceptions for other data ...
- 03:09 PM Feature #3813: misc DB features part deux
- On the conversion of the field definition...
- 02:56 PM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> Eric Faulhaber wrote:
> > Where @foo@ represents a DMO and @bar@ is a @decimal@ property, ... - 01:33 PM Feature #3813: misc DB features part deux
- @DEFAULT-STRING@ uses only decimal separator when rendering @DECIMAL@ values. The value of the group separator is not...
- 11:04 AM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> No. A format string is not the same thing as the @DATE-FORMAT@. A format string for @date@ migh... - 10:45 AM Feature #3813: misc DB features part deux
- > DEFAULT-STRING renders its dates and numeric values in LOCAL format, subject to the DATE-FORMAT and NUMERIC-FORMAT ...
- 08:23 AM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> The @date@, @datetime@, @datetime-tz@, @integer@, @int64@ and @decimal@ classes all are designed ... - 08:14 AM Feature #3813: misc DB features part deux
- The @date@, @datetime@, @datetime-tz@, @integer@, @int64@ and @decimal@ classes all are designed to format their stat...
- 07:51 AM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Igor Skornyakov wrote:
> > Do we have methods for rendering date/numeric data using @SESSION:DAT... - 07:46 AM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> > We need to correctly distinguish between datetime literal and valid expression as NOW. The firs... - 07:39 AM Feature #3813: misc DB features part deux
- > We need to correctly distinguish between datetime literal and valid expression as NOW. The first question is what c...
- 07:36 AM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> Do we have methods for rendering date/numeric data using @SESSION:DATE-FORMAT@ and @SESSION... - 05:45 AM Feature #3813: misc DB features part deux
- Do we have methods for rendering date/numeric data using @SESSION:DATE-FORMAT@ and @SESSION:NUMERIC-FORMAT@ attribute...
- 05:39 AM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> Where @foo@ represents a DMO and @bar@ is a @decimal@ property, the following will return th... - 04:40 AM Feature #3813: misc DB features part deux
- The issue described in the #3813-97 was a result of the following. I've compiled two tests. The TEMP-TABLE @source-da...
- 03:35 AM Feature #3813: misc DB features part deux
- Eric Faulhaber wrote:
> Where @foo@ represents a DMO and @bar@ is a @decimal@ property, the following will return th...
04/06/2020
- 07:29 PM Feature #3813: misc DB features part deux
- Where @foo@ represents a DMO and @bar@ is a @decimal@ property, the following will return the value of DECIMAL from t...
- 05:43 PM Feature #3813: misc DB features part deux
- Igor Skornyakov wrote:
> I cannot find where the value of the DECIMAL option of the field definition is located in t... - 05:38 PM Feature #3813: misc DB features part deux
- I cannot find where the value of the DECIMAL option of the field definition is located in the conversion artifacts.
... - 01:35 PM Feature #3813: misc DB features part deux
- Ovidiu Maxiniuc wrote:
> I will schedule working on this issue. 4011a is not yet stable enough, but we'll see whethe... - 01:29 PM Feature #3813: misc DB features part deux
- > BTW: do I understand correctly that more complicated expressions cannot be used in the @INITIAL@ clause?
TBH, befo... - 12:40 PM Feature #3813: misc DB features part deux
- Ovidiu Maxiniuc wrote:
> I am working on 4011a branch, where the field's attributes (including the default value) ar... - 12:29 PM Feature #3813: misc DB features part deux
- The following field definition...
- 12:26 PM Feature #3813: misc DB features part deux
- I am working on 4011a branch, where the field's attributes (including the default value) are defined as DMO interface...
- 11:40 AM Feature #3813: misc DB features part deux
- At the moment FWD runtime support if the INITIAL attribute for fields like @FIELD s-datetime AS DATETIME INITIAL NOW@...
- 09:57 AM Feature #3813: misc DB features part deux
- Greg Shah wrote:
> Doesn't the @DEFAULT-VALUE@ of the DMO map more closely to @BUFFER-FIELD:DEFAULT-VALUE@ instead o... - 09:50 AM Feature #3813: misc DB features part deux
- Doesn't the @DEFAULT-VALUE@ of the DMO map more closely to @BUFFER-FIELD:DEFAULT-VALUE@ instead of using the @DEFAULT...
- 09:42 AM Feature #3813: misc DB features part deux
- We have no support for the BUFFER-FIELD:DEFAULT-VALUE (even conversion is not supported). This can be a little bit tr...
- 07:34 AM Feature #4011: database/persistence layer performance improvements
- Eric Faulhaber wrote:
> Which revision of hotel_gui are you using with 4011a/11404?
I found r202 of hotel_gui is wh...
04/05/2020
- 06:08 PM Feature #4011: database/persistence layer performance improvements
- Ovidiu Maxiniuc wrote:
> I have committed my latest changes to 4011a as r11404.
> The standalone hotel_gui is start... - 07:52 AM Feature #4011: database/persistence layer performance improvements
- I have committed my latest changes to 4011a as r11404.
The standalone hotel_gui is starting up and tabs can be navig... - 07:37 AM Feature #4011: database/persistence layer performance improvements
- > This is a non-orthodox workaround.
You're being kind. Let us call it what it is: an ugly solution. Unfortunate...
04/04/2020
- 06:24 PM Feature #4011: database/persistence layer performance improvements
- Greg, thanks for suggestion. This is a non-orthodox workaround. Here is what I've done.
I altered @NUM_LITERAL@ in l...
04/03/2020
- 06:33 PM Feature #3813: misc DB features part deux
- By the end of the weekend, please report the list of open items remaining in this task. We can push the #3813-81 it...
- 06:31 PM Feature #4011: database/persistence layer performance improvements
- Is the column name version of @order@ always "qualified" (e.g. @tt1.order@)? If so, then you can easily differentiat...
- 05:29 PM Feature #4011: database/persistence layer performance improvements
- In fact, @by@ does not suffer from this inconvenient as it is already a Progress reserved keyword and cannot be the n...
- 04:59 PM Feature #4011: database/persistence layer performance improvements
- I encountered the following issue and I see no easy trick to work around. It is a antlr issue I think. Suppose we hav...
04/02/2020
- 08:22 AM Feature #3813: misc DB features part deux
- Contrary to what is said in the Progress documentation the @DEFAULT-STRING@ attribute is read-only. This is logical a...
04/01/2020
- 11:47 AM Feature #4011: database/persistence layer performance improvements
- Greg Shah wrote:
> > There is another issue which I have in mind: when creating a savepoint, shouldn't we also sav... - 11:36 AM Feature #4011: database/persistence layer performance improvements
- Greg Shah wrote:
> What happens if in the meantime between the roll-forward and the original execution of a statem... - 07:39 AM Feature #4011: database/persistence layer performance improvements
- > maybe, instead of trying to track NO-UNDO DMOs as POJOs, I need to track the SQL statements that were rolled back a...
- 07:21 AM Feature #4011: database/persistence layer performance improvements
- Eric, this FFD replay is the same though I had in mind. I don't think we can keep the database in good condition and ...
Also available in: Atom