Activity

From 06/09/2014 to 07/08/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... Greg Shah
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. Greg Shah
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... Constantin Asofiei

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... Hynek Cihlar
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... Ovidiu Maxiniuc

05:39 AM Bug #2327: Wrong values initialized by field initializer: The following program... Hynek Cihlar
05:38 AM Bug #2327 (New): Wrong values initialized by field initializer: Hynek Cihlar
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... Constantin Asofiei

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... Hynek Cihlar
05:03 PM Bug #2326: Reference to the extent value of a field is emitted as a constant: The 4GL code... Hynek Cihlar
04:54 PM Bug #2326 (New): Reference to the extent value of a field is emitted as a constant: Hynek Cihlar

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... Eric Faulhaber

12:35 PM Feature #2220: dynamic query methods which require implementation: Sample looks good, thanks. Eric Faulhaber
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 ... Stanislav Lomany
11:34 AM Feature #2220: dynamic query methods which require implementation: Testcase:... Stanislav Lomany

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... Eric Faulhaber
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... Eric Faulhaber

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... Ovidiu Maxiniuc
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... Eric Faulhaber

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... Ovidiu Maxiniuc
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... Ovidiu Maxiniuc

03:55 PM Feature #2312: match Progress collation in a SQL Server database: Ovidiu Maxiniuc wrote:
> The order in which strings are sorted in p4gl is detected by the attached Progress procedur... Eric Faulhaber
02:20 PM Feature #2312: match Progress collation in a SQL Server database: Forgot to add collation test for Sql Server. Ovidiu Maxiniuc
02:19 PM Feature #2312 (WIP): match Progress collation in a SQL Server database: I am not sure we create a user-defined collation in SQL Server :(. From my research we have to be lucky enough to fin... Ovidiu Maxiniuc

05:02 PM Feature #2312: match Progress collation in a SQL Server database: When sorting on a text column, Progress sorts its rows differently in certain cases than PostgreSQL does by default, ... Eric Faulhaber

11:41 AM Feature #2319: support for dialect-specific keywords in NameConverter: Because each SQL dialect has its own set of reserved keywords the @NameConverter@ must be aware and convert the names... Ovidiu Maxiniuc
11:12 AM Feature #2319 (New): support for dialect-specific keywords in NameConverter: Ovidiu Maxiniuc

Also available in: Atom

FWD » Core Development » Database