Activity
From 06/14/2014 to 07/13/2014
07/13/2014
- 03:35 PM Bug #2295: In Progress output parameters ignore decimal precision
- The case above from note 1 has been fixed by #2293.
07/12/2014
- 06:27 PM Bug #2295 (WIP): In Progress output parameters ignore decimal precision
- 01:43 PM Bug #2337: trigger scanning defect
- I converted the customer's server project. The @schema-triggers.xml@ file is left at the project root directory, but ...
07/11/2014
- 03:35 PM Bug #2337 (WIP): trigger scanning defect
- Code review 20140711a:
The only comment I have is about the change in approach when initializing the trigger manag... - 02:28 PM Bug #2337 (Review): trigger scanning defect
- Uploaded fix for trigger issues:
- the @schema-trigger.xml@ improved in the second step
- @DatabaseTriggerManager@ ... - 11:32 AM Bug #2337: trigger scanning defect
- Ah, OK. Sorry for the confusion I caused.
- 11:30 AM Bug #2337: trigger scanning defect
- I see, for the customer, @com/something/server/dmo@, it make more sense.
I was fooled by "directory's parent". I int... - 11:22 AM Bug #2337: trigger scanning defect
- Ovidiu Maxiniuc wrote:
> I will add the rule for copying the file to @run/server@ and load it accordingly.
I foll... - 06:36 AM Bug #2337: trigger scanning defect
- I found the cause why ASSIGNS are not converted correctly.
In the @progress.g@, in the @on_stmt@ function, the follo... - 05:00 AM Bug #2337: trigger scanning defect
- Eric Faulhaber wrote:
> I would not add this to the root of the jar, if it is associated with a particular schema (@...
07/10/2014
- 06:07 PM Bug #2337: trigger scanning defect
- Ovidiu Maxiniuc wrote:
> Fixed the issue. It proved to be rather simple, just to add the class name (including packa... - 04:29 PM Bug #2337 (WIP): trigger scanning defect
- Fixed the issue. It proved to be rather simple, just to add the class name (including package to current xml list of ...
- 12:16 PM Bug #2337: trigger scanning defect
- Because File.listFiles() does not work on jar locations, the initialization of the @DatabaseTriggerManager@ (gatherin...
- 12:11 PM Bug #2337 (Closed): trigger scanning defect
07/09/2014
- 05:08 PM Bug #2336: TABLE-HANDLE FOR parameters for internal procedures
- TABLE-HANDLE FOR parameters for internal procedures are not converted properly. @appserver-table-errors.p@ and @appse...
- 05:04 PM Bug #2336 (New): TABLE-HANDLE FOR parameters for internal procedures
07/02/2014
- 06:27 AM Bug #2327: Wrong values initialized by field initializer
- This is a database issue more than a base language issue.
Eric will determine if this needs to be worked now, or i... - 06:20 AM Bug #2326: Reference to the extent value of a field is emitted as a constant
- This task is related to database conversion more than base language.
It does not need to be worked on right now. - 03:51 AM Bug #2295: In Progress output parameters ignore decimal precision
- Hynek Cihlar wrote:
> The case above from note 1 has been fixed as part of the issue #2293, and about to be released...
07/01/2014
- 05:15 PM Bug #2295: In Progress output parameters ignore decimal precision
- The case above from note 1 has been fixed as part of the issue #2293, and about to be released.
A similar case exi... - 09:41 AM Feature #2312: match Progress collation in a SQL Server database
- I have run some scans over the database dump from lincon01, indexing the occurrences for each character in strings. I...
06/30/2014
- 05:39 AM Bug #2327: Wrong values initialized by field initializer
- The following program...
- 05:38 AM Bug #2327 (New): Wrong values initialized by field initializer
- 03:28 AM Bug #2326: Reference to the extent value of a field is emitted as a constant
- Hynek Cihlar wrote:
> If I am correct, fields can be declared as determinate extents only (with a constant extent si...
06/29/2014
- 05:09 PM Bug #2326: Reference to the extent value of a field is emitted as a constant
- If I am correct, fields can be declared as determinate extents only (with a constant extent size) hence this issue ma...
- 05:03 PM Bug #2326: Reference to the extent value of a field is emitted as a constant
- The 4GL code...
- 04:54 PM Bug #2326 (New): Reference to the extent value of a field is emitted as a constant
06/27/2014
- 06:29 PM Feature #2312: match Progress collation in a SQL Server database
- Please choose from the available collations the ones you feel are the closest, practical matches for Progress' collat...
06/25/2014
- 12:35 PM Feature #2220: dynamic query methods which require implementation
- Sample looks good, thanks.
- 11:58 AM Feature #2220: dynamic query methods which require implementation
- > Looks good, though I would still like to see sample output. Note there is another version of @IndexHelper@ in play ...
- 11:34 AM Feature #2220: dynamic query methods which require implementation
- Testcase:...
06/24/2014
- 07:13 PM Feature #2220: dynamic query methods which require implementation
- Code review 0604a:
Looks good, though I would still like to see sample output. Note there is another version of @I... - 06:45 PM Feature #2220: dynamic query methods which require implementation
- I am reviewing the 0604a update now (sorry it took so long for me to get to this). Could you please post some test ca...
06/20/2014
- 09:57 AM Feature #2312: match Progress collation in a SQL Server database
- Reading [[http://technet.microsoft.com/en-us/library/ms175194(v=sql.110).aspx]], I understand that SQL Server has a b...
- 07:42 AM Feature #2312: match Progress collation in a SQL Server database
- Is it possible to create new collations/locales for Windows itself (as we do on Linux) and then use these with SQL Se...
06/16/2014
- 05:36 PM Feature #2312: match Progress collation in a SQL Server database
- Apparently none of available collations are good enough.
Attached a spreadsheet with summary of the research.
* 1st... - 04:53 AM Feature #2312: match Progress collation in a SQL Server database
- As expected, the order is the same on both windows and linux implementations. The output file is attached.
I go o...
Also available in: Atom