abbreviations: * DSE Data Source Explorer * CUI Character User Interface * GUI Graphical User Interface * IT Information Technology
Dear OO Base team and community: I stumbled upon the following DSE problems during a test of OO Base feasibility for business usage. I would appreciate advice on how to resolve them. Thanks. Ray ----- * DSE corrupted unicode content All Unicode content is corrupted during insertion in batch mode (10k - 20k rows) from DSE in 2.0.4 OO Calc into OO Base. Unicode display is OK for OO Calc content. Unicode display is OK for OO Base content displayed through DSE inside OO Calc. Unicode insertion is OK for OO Base HSQLDB CUI (Tools - SQL, both embedded and stand alone). Unicode support is mandatory in a global business environment. The IT team and the target client can and often operate in different geographic areas. Or one can regard Unicode as an expanded market reach if the (human) language is not an obstacle for the IT team. Is there a button to enable the Unicode content insertion into OO Base through DSE in OO Calc? * DSE for more than 10k - 20k source rows What is the extra warning about "... value too large ..." during the insertion of more than 10k - 20k rows through DSE in OO Calc into OO Base? Is it about the source data content? Is it about something else? Does it change or corrupt the data input, and which rows? * DSE table name in data insertion Users should be able to drag the source range in OO Calc unto a table in DSE, not just the "Tables" section title. The selected table in DSE should be the default table name for data insertion through DSE, subject to user revision in case of mis-drop during the drag-and-drop. OO Base object already knows the distinction between true tables and views inside the Table container. DSE GUI should be revised to allow the tables (not views) inside the "Tables" container as permitted drop targets. * DSE for Identity columns Null in source range will fail insertion into Identity columns through DSE in OO Calc. Arbitrary numbers have to be assigned in OO Calc source ranges for insertion into Identity columns. This is impractical for data appending operation as the current Identity() state is required to not cause insertion failure (an undesireable scenario of database repair). It is also impractical to require casual users (not DBA) reponsible for data input to handle this issue. Insert Into user_table Values ( Null, ... ) -- for Identity columns Insertion of Null into Identity columns is OK through OO Base HSQLDB CUI (Tools - SQL). * DSE batch indicator Currently DSE in OO Calc does not clear the dialog windows before the execution of data insertion into OO Base. The display is mangled and frozen for some time during the insertion of large amount of data (10k - 20k rows, and more). It would be better to close and clear all dialog windows, switch focus back to the previous window (likely the source range in OO Calc), perhaps pop up a small progress dialog (can be static to save CPU), so that users know the program did not hang. * DSE batch error processing The current dialog for data insertion through DSE in OO Calc into OO Base is designed only for interactive operation. In batch data insertion (> 20k rows), there is no way to record data rows (can be many) that fail the SQL execution, possibly due to violation of referential integrity, etc., as stipulated by database design. Need an additional dialog for user specified location of cell range into which all offending source data rows will be recorded for post mortem diagnosis. * DSE interactive error processing Interactive operation is useful for small scale testing. The current error message is of no value: Insert Into user_table Values ( ?, ?, ?, ... ) It is probably directly dumped from JDBC PreparedStatement code. All "?" should be replaced with actual user data content, since DSE already holds the info. for JDBC PreparedStatement. * DSE ad-hoc connection to data source This issue has been previously discussed in this forum. Users should be able to connect to data sources ad-hoc inside DSE, without registration of data sources. Users should not have to switch out of DSE, move to a separate GUI (currently Tools - Options - Base etc.), register the selected data sources, switch back to DSE, and then continue data analysis. This need of ad-hoc connection emerges mostly for analysis and decision making based on multiple data sources. Such operating styles occur often in larger business entities, with resources to collect and process multiple types of info., in contrast to smaller business operations. ________________________________________ PeoplePC Online A better way to Internet http://www.peoplepc.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
