Activity
From 11/05/2017 to 12/04/2017
11/27/2017
- 03:46 PM Bug #3372 (Closed): Unexpected usage of standalone unknown value.
- Branch 3369a was merged to trunk as revision 11206.
11/21/2017
- 12:55 PM Bug #3379: do not copy index definitions when defining WORKFILE like TABLE
- A customer pointed out that when defining a WORKFILE using LIKE to copy the definition of a table, index information ...
- 12:52 PM Bug #3379 (Closed): do not copy index definitions when defining WORKFILE like TABLE
11/20/2017
- 07:45 AM Bug #3372 (WIP): Unexpected usage of standalone unknown value.
- Fix committed revision 11206 in 3369a.
- 07:43 AM Bug #3372: Unexpected usage of standalone unknown value.
- Eric Faulhaber wrote:
> Please put this into task branch 3296a if it does not have a home yet.
Sorry, I meant 3369a. - 07:35 AM Bug #3372: Unexpected usage of standalone unknown value.
- Ovidiu Maxiniuc wrote:
> I decided to skip the injection of @rtrim@ if the node is marked as @unknown@. The result w...
11/17/2017
- 01:30 PM Bug #3372: Unexpected usage of standalone unknown value.
- After further investigations I learned that the @rtrim@ was injected after collecting @toString@ node to list of unkn...
- 11:59 AM Bug #3372: Unexpected usage of standalone unknown value.
- FWD jumps to login screen in customer application. Searched logs and found the following exception listed as the root...
- 11:46 AM Bug #3372 (Closed): Unexpected usage of standalone unknown value.
11/08/2017
- 03:28 PM Bug #3367: collision between sequence and table names
- Eric Faulhaber wrote:
> ...I plan to run a quick conversion regression test...
Never mind, I see you did that alrea... - 02:05 PM Bug #3367: collision between sequence and table names
- Code review 3367a/11197:
Thank you for the quick turnaround on this fix.
The code looks fine to me, with the ca... - 01:25 PM Bug #3367: collision between sequence and table names
- Ovidiu Maxiniuc wrote:
> There is a small inconvenient. Because in @.df@ file the @employee@ sequence is declared be... - 12:49 PM Bug #3367: collision between sequence and table names
- The standard conversion test on devstv01 finished as expected, without any changes in generated code.
The @convert... - 11:20 AM Bug #3367: collision between sequence and table names
- Although at first I tried to fix the issue in TRPL I realized that @NameConverterWorker@ is a better place. It can st...
- 03:53 AM Bug #3367 (WIP): collision between sequence and table names
- Constantin found the following exception in log while doing an import:...
- 03:28 AM Bug #3367 (WIP): collision between sequence and table names
Also available in: Atom