IIUG - Feature Request Survey #1

As I mentioned in my previous message, here is the first installment of the IIUG Feature Request Survey. As the process matures, we will build other methods for you to give us input. This first survey includes data from Informix's feature request database as well as ideas generated from a comp.databases.informix discussion thread started by Tim Schaefer. Carlton Doe President, IIUG carlton@iiug.org ----------------------------------------------------------------------- HOW DO I DO THIS? It's very simple. You have 100 IIUG "credits" to allocate to those ideas you think are important. You can apply as many or as few credits to any one item depending on how valuable that feature is to you. Some ideas ask for additional input or information. Please be considerate of us who have to read each comment--give us *one* idea and keep your comments short and to the point. When you complete this survey, return it to the IIUG c/o the following e-mail address: survey_results@iiug.org We will tabulate the results and let you know what happened. We realize there is not much time before the Informix conference later this month. The sooner you can get your survey back to us, the better. Thanks!!! The IIUG Board of Directors IIUG FEATURE REQUEST SURVEY #1 # of Credits _______ case insensitive search _______ faster update statistics _______ external archive checker _______ union views _______ bit mapped indexes _______ star join optimization _______ table level backup _______ reduced resource utilization (memory) _______ better connection management _______ JDBC support _______ C++ support _______ gateway enhancements (specify) ______________________________________________________________ _______ DSS performance enhancements (specify) ______________________________________________________________ _______ OLTP performance enhancements (specify) ______________________________________________________________ _______ HA (failover) _______ Wolfpack support _______ NT enhancements (specify) ______________________________________________________________ _______ attach/detach fragment _______ backup/restore enhancements (specify) ________________________________________________________________ _______ load enhancements (specify) ________________________________________________________________ _______ configuration enhancements (client or server) _______ IECC (graphical admin) on UNIX _______ web administration _______ XPS enhancements (specify) _________________________________________________________________ _______ CORBA support _______ DCOM support _______ OLE DB support _______ Better tools integration with (specify tool) ______________________________________________________________________ _______ middleware integration _______ hierarchical replication _______ synchronization _______ messaging integration/support _______ Windows 95 database support _______ enhanced support for third party applications _______ Port ODS 7.x, 4GL, SE, ISQL, ESQL/C to Linux. _______ Shrink_wrap New Era. Drop the run_time licensing fees. _______ Fix 4GL and adopt the changes proposed long ago by others. _______ Improve Online installation (specify). ________________________________________________________________ _______ Rewrite PC network connectivity (specify). ________________________________________________________________ _______ Bundle commonly used products--WEB, Client/server, tools, and networking in one offering. _______ A function (similar in use to "extend") to handle UTC time directly from SQL. Usage should be something like: select LOCAL_DATE(utc_column, year to second) from . . . The function should automatically determine offset from GMT in the same manner as the OS, be year 2000 compliant, and take an integer column as input. _______ Informix CD_DOC available in HTML format. _______ Provide more information on the query profile (aka Set Explain) in the SMI. _______ Provide an option for cumulative total for light scans. _______ Enable Microsoft Transaction Server to talk to an Informix database. _______ Upper/lower preview of estimated query costs. _______ Sqexplain logs with watermarks for costs and uid. _______ Enhance CLI/ODBC security (specify). ______________________________________________________________________ _______ Long table and column names. _______ Full SQL_92 compliance. _______ Right justification attribute in .per forms. _______ 'IN' and 'NOT IN' syntax that allows more than one field. _______ A mechanism for the engine to silently add a temporary log to handle rollbacks of live transactions (cf tbone). _______ Put threads to sleep that are spinning unproductively. Re_awaken when needed. _______ Paralellize dbexport/import. _______ Give onunload/load an option to retain source dbspace names (like an -ss option). _______ Allow a value in place of a null within a query. _______ Enhance SQLCA to include the ID of the current connection, the name of the current database, the statement ID of the statement just executed, the cursor ID of the most recent FETCH or PUT, the name of a constraint that was violated. _______ A data dictionary incorporated into the database overhead tables that allows entry of documentation for each object. _______ Easier utility to cross_reference thread to VP utilization. _______ TRUNCATE TABLE command. _______ Provide sqlidebug/sqliprint for all versions of ODS on all platforms. _______ Publicize a patch list. _______ Implement tape device checks and basic tape handling in the Ontape and Onarchive utilities. _______ Java in the engine. _______ Extend the SPL (specify). ____________________________________________________________________ _______ Implement UPSHIFT/DOWNSHIFT and other functions in every engine. _______ Windows that can be written to "underneath" others in 4GL. _______ Improve string manipulation functions in SQL, SPL and 4GL. (ie. Snobol or old Honeywell tex). _______ 4GL fields than can abut other fields and text, ie get rid of the [] delimiters in the screen section. _______ Scrolling forms in 4GL. _______ Positionable INPUT and DISPLAY ARRAY statements in 4GL, so you can move the cursor and array around under programmatic control. _______ Allow array members not visible on the screen to be "carried along" by INPUT ARR