Re: INFORMIX WISH LIST

OK, Tim, I'm sold, here's my pet peeve(s): 1. Whenever a dialup user/client connects to the database and selects a BLOB column (which typically moves slowly across the phone line...), the engine thread driving the communication spins as fast as it can trying to write to the socket, even though it can only write probably once per million spins. The rest is all wasted. I think the thread should sleep between writes, at least for slow connections. Wakeup simply can't be that expensive. The net effect is that this screws up my capacity planning because after the fact, I cant distinguish between productive work and nonproductive spinning (which for me can be substantial). This problem doesn't occur when garden variety result sets are being transmitted. 2. Primary keys of fragmented tables always go in the dbspace the database was created in, no way to relocate them or fragment them that I can find. The doc says its "for performance reasons", but I sure don't see why this should perform better, it's probably worse, to say nothing of the space hassles you can create if you're not real careful. I'd like to have the same options non PK indexes have. 3. Most utilites could be improved. dbexport/import could be more flexible and parallel. onunload/load could use an option to retain source dbspace names (like -ss option I guess...). Greg Tim Schaefer wrote: snip.....