Activity
From 08/15/2017 to 09/13/2017
09/06/2017
- 08:43 PM Feature #3319: investigate viability of using the Progress database as a back-end
- You are correct in your assumption. I was just trying with both the UDF support and the schema to try and see what m...
- 08:11 PM Feature #3319: investigate viability of using the Progress database as a back-end
- Christopher Cotter wrote:
> I am working on getting the hotel table and index ddl files applied to OE 11.7.
>
> I...
09/05/2017
- 07:38 PM Feature #3319: investigate viability of using the Progress database as a back-end
- OE SQL Reserved Words List
http://knowledgebase.progress.com/articles/Article/000049334
- 06:50 PM Feature #3319: investigate viability of using the Progress database as a back-end
- I am working on getting the hotel table and index ddl files applied to OE 11.7.
It's mostly working with the excep...
09/02/2017
- 09:57 PM Feature #3319: investigate viability of using the Progress database as a back-end
- Christopher Cotter wrote:
> Changing "double precision" to "decimal" and "datetime2" to "timestamp" seemed to do the...
09/01/2017
- 07:52 PM Feature #3319: investigate viability of using the Progress database as a back-end
- Changing "double precision" to "decimal" and "datetime2" to "timestamp" seemed to do the trick. What are the potenti...
- 06:37 PM Feature #3319: investigate viability of using the Progress database as a back-end
- I am having some success but running into this error. Maybe something to do with the "double precision" datatype? I ...
- 04:15 PM Feature #3319: investigate viability of using the Progress database as a back-end
- Something like this works. Different syntax but similar idea.
How much effort would be needed to add a progress o... - 02:03 PM Feature #3319: investigate viability of using the Progress database as a back-end
- BTW, I don't know if you're just interested in the SQL Server DDL FWD generates, or if you actually want to get Hotel...
- 01:30 PM Feature #3319: investigate viability of using the Progress database as a back-end
- Christopher Cotter wrote:
> So it sounds like these constructs are custom java work needed to support SQL Server?
Y... - 01:11 PM Feature #3319: investigate viability of using the Progress database as a back-end
- So it sounds like these constructs are custom java work needed to support SQL Server?
3. the p2j2clr.dll assembly ... - 12:47 PM Feature #3319: investigate viability of using the Progress database as a back-end
- Ok, so there is a second "shim" layer in the @p2j.dll@ assembly that we don't have for the "pure Java" UDF implementa...
- 12:24 PM Feature #3319: investigate viability of using the Progress database as a back-end
- I am not sure whether SQL Server has a @CREATE ALIAS@ statement, but the FWD mechanism that replaces the overloaded f...
- 12:00 PM Feature #3319: investigate viability of using the Progress database as a back-end
- Christopher Cotter wrote:
> Is the CREATE ALIAS really necessary? Is there a reason all of the UDF parameters could... - 11:41 AM Feature #3319: investigate viability of using the Progress database as a back-end
- Does this use the same runtime mapping as we use for UDFs overloaded with CREATE ALIAS (i.e., to map an undecorated U...
- 11:26 AM Feature #3319: investigate viability of using the Progress database as a back-end
- Eric Faulhaber wrote:
> Ovidiu, didn't you have to deal with UDF overloading without CREATE ALIAS for SQL Server?
... - 11:16 AM Feature #3319: investigate viability of using the Progress database as a back-end
- Looks like on OE there is a CREATE SYNONYM rather than CREATE ALIAS
https://documentation.progress.com/output/ua/O... - 11:15 AM Feature #3319: investigate viability of using the Progress database as a back-end
- Question via email:
> Looks like on OE there is a CREATE SYNONYM rather than CREATE ALIAS
>
> https://documentatio... - 05:56 AM Bug #3324: Incorrect handling of temp tables with the same name makes translated code non-compilable
- This is not a bullet-prof solution. There are still cases when this kind of name collisions can occur. We need to thi...
- 08:24 PM Bug #3324: Incorrect handling of temp tables with the same name makes translated code non-compilable
- This fix is checked in to branch 3330a which we intend to put through testing starting this weekend. It will be merg...
- 08:23 PM Bug #3324: Incorrect handling of temp tables with the same name makes translated code non-compilable
- From Ovidiu, working in #3330-277 which is the same root cause:
> I think I have a slight idea about what is wrong...
08/31/2017
- 02:20 PM Feature #3319: investigate viability of using the Progress database as a back-end
- We already deal with database dialects which do not support "native" UDF overloading. In this case, we internally ove...
- 09:34 PM Feature #3319: investigate viability of using the Progress database as a back-end
- This seems to work and might be a generic solution to the overloading problem.
rop function eq;
create function... - 08:57 PM Feature #3319: investigate viability of using the Progress database as a back-end
- Openedge SQL Data Type Mappings
https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmsql/d... - 08:39 PM Feature #3319: investigate viability of using the Progress database as a back-end
- I created a sports2000 database and used these commands to get the ball rolling.
c:\progress\openedge\bin\sql_env
... - 08:34 PM Feature #3319: investigate viability of using the Progress database as a back-end
- I did some testing on OE 11.7 today using the SQLExplorer and running just a SQL server process instance.
It doesn...
08/25/2017
- 01:37 PM Feature #3296: misc db features
- There is a use of a table parameter with BY-REFERENCE. Is this handled already by conversion?
- 12:43 PM Feature #3294: implement temp-table XML support from #3257-34
- Greg Shah wrote:
> The conversion changes for this task (branch 3293a) were merged to trunk on 08/24/2017 as revisio... - 12:08 PM Feature #3294: implement temp-table XML support from #3257-34
- The conversion changes for this task (branch 3293a) were merged to trunk on 08/24/2017 as revision 11160.
The gap ...
08/24/2017
- 11:49 AM Bug #3315: infinite loop in mark_client_branch during annotations because of nest CAN-FINDs with ...
- The patch from #3315-2 was added to task branch 3293a, which was merged to FWD trunk revision 11160.
Jaroslaw, at ... - 09:26 AM Feature #3293 (WIP): implement metaschema usage from #3257-3
- Task branch 3293a contains conversion support for the missing metadata features. It was merged and committed to trunk...
Also available in: Atom