Activity
From 05/29/2014 to 06/27/2014
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...
06/13/2014
- 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... - 02:20 PM Feature #2312: match Progress collation in a SQL Server database
- Forgot to add collation test for Sql Server.
- 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...
06/12/2014
- 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, ...
06/10/2014
- 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...
- 11:12 AM Feature #2319 (New): support for dialect-specific keywords in NameConverter
06/04/2014
- 06:34 PM Feature #2220: dynamic query methods which require implementation
- Update for review with indexInformation implemented.
06/03/2014
- 04:51 PM Bug #2315: CAN-FIND() conversion throws exception if record is unavailable for WHERE clause.
- Details are in issue #2301, notes 32, 34, 35.
- 04:49 PM Bug #2315 (Closed): CAN-FIND() conversion throws exception if record is unavailable for WHERE cla...
- 04:32 PM Feature #2314: make the _meta database conversion and runtime optional
- For projects which don't require/use the metadata DB, the conversion process should not generate the @dmo._meta@ DMO'...
- 04:31 PM Feature #2314 (New): make the _meta database conversion and runtime optional
06/02/2014
- 03:45 PM Feature #2313 (Hold): match Progress collation on a PostgreSQL database on Windows
- 03:44 PM Feature #2312 (WIP): match Progress collation in a SQL Server database
- 12:15 PM Bug #18: issues with ne/equal and true/false conversion in WHERE clauses
- This task is not known to affect any customer code; removing from M11 accordingly. If testing indicates otherwise, we...
05/30/2014
Also available in: Atom