Re: Whatcha' wanta have?????

Madison Pruet wrote: > > As a mild diversion from the IDS-DB2 conversion thread, its time for one of > my more favorite exercises. ;-) > > We are nearing the end of the coding cycle for IDS 9.5. We've got a whole > bunch of really cool stuff in place and - well - its time to get input from > you guys as to what you want to see in the 9.6 release. > > Now, I know that everyone's favorite thing is going to be "marketing", but > I'm in development. So I need to talk features and functionality. So feel > free to send them on in. > > Just an FYI - I'll be away for a while and won't be able to get email via my > comcast email address. But, I'll be following the newsgroup rather closely. > > Also, next week I'll be in some planning meeting. So getting responses back > fairly quickly would really help. > > Thanks > > M.Pruet I' d like to see - physlog inital setup much like rootdbs - same for loglog so that one does not have to do the ever same steps at the very beginning - when auto build indexes (at reinable constraints time) automatic adjustment along a ressource spec or test of available filesystems / memory so that it is not a crawl (like now) - automatic usage of memory in update statistics for sorts, if memory is around in tons (like it tends to be now everywhere) - better documentaion of the ER internal tables used for conflict resolution like: when does it go to the dbspace the db was created in (gramented tables) or when does it sit in the dbspace where the table is.... All that is rather documented not enough to avoid problems of running out of space - a new warning if you load zillions of records into a table with using default FIRST SIZE of 8 pg - a warning from update statistics if # of datapages is much smaller then pages used & indexes are not on that table or only detached ones. - a way to tell in what file one wants output of SET EXPLAIN ON dic_k -- Richard Kofler SOLID STATE EDV Dienstleistungen GmbH Vienna/Austria/Europe