OpenEdge Database - Products Enhancements - Progress Community
ANNOUNCEMENT - November 11, 2019

The submission of Ideas (product feature enhancements) will be migrated to a new and significantly improved platform in the December 2019 time frame. When the change takes place, you will be redirected to the new location.

Please note that existing open Ideas in this Community are being imported into the new system.

 OpenEdge Database

  • Implement control on database logging (.lg) verbosity and type of events to include...

    • Under Review
    • 2 Comments
    Implement setting on the database side to control the verbosity of the logging and to be able to exclude some types of log events. In our case the database .lg file gets flooded with: P-2359410 T-1 I ABL 7: (7129) Usr 7 set name to batch@xxxx.com. P...
  • Make VST date+time fields DATETIME instead of CHARACTER

    The subject explains it all: VST tables are filled with dates and times, for instance _Connect._Connect-Time these fields are always (except possibly _KeyEvt._KeyEvt-Date) character fields. Make them datetime(-tz) instead, or add corresponding datetime...
  • Make Progress OpenEdge multi-threaded

    • Not Planned
    • 1 Comments
    As we all know, Progress is single-threaded. You can only do one thing at a time. If a user wants to multi-task, they have to open up another application session which A) May have licensing implications and B) Is kludge in the eyes of the end-user. A...
  • Have an option on backup to generate a dbanalys file

    • Not Planned
    • 2 Comments
    This has been on the list for years, but I will give you a specific use case so you can understand that not having this incurs additional downtime. Dump and load processing looks like this: Shutdown Backup - 30 minutes Dbanalys - 30 minutes...
  • Please document *ALL* utility parameters

    This is perhaps more of a bug (or collection of bugs) than a request for an "enhancement". Please compare the parameters implemented in the code to the parameters listed in the documentation. There are a lot of parameters that are not documented...
  • Add index on _UserTableStat and _IndexTableStat

    If I want to find out Index and Table usage stats for a particular user I use the code below. It works fine but it's ridiculously slow, as is the one on _IndexTableStat that's similar. Please could an index for _UserTableStat-Conn and _UserIndexStat...
  • Add support for multiple collations in one database

    In a multi-lingual application, you can only have one database collation which determines the sorting of indexes. Since there are different sorting rules for different languages, it should be possible to use several collations. Allow loading several...
  • Get DLC version info from a backup file

    It can be difficult to determine which Progress version created a backup file. The request is for syntax like prorest <db> <backup> -version, or alternatively, just add the DLC version info to prorest -list output. Thanks to Stefan Drissen...
  • Make trigger r-code reside in the database

    • Under Review
    • 3 Comments
    Replication and Schema triggers r-code should be stored in the database. The CRUD operations cannot work without them. Currently if your PROPATH is not setup properly if an operation causes a trigger to fire, the code will not be found. If the r-code...
  • Automatically enable large files

    Enabling large files should be a standard behavior when creating a new database with f.e. prostrct create. Now you have to do this in a separate step, which is often forgotten.