Known Bugs in MyOra 1.0.2
Known Bugs in MyOra 1.0.0
Known Bugs in MyOra 1.0.1
Known Bugs in MyOra 1.0.4
- Bug # 01003 - Date/Time format error in SQL Editor:
The date/time format string in a SQL statement is interpreted as a bind variable and prompts for data input.
When a SQL statement is run with HH:MI:SS as part of date/time format, a popup dialog prompts for data input.
Temporary workaround: Press OK or Cancel button on the popup dialog to execute SQL statement without error.
The date/time in the result data is not formatted correctly for a SQL SELECT statement with a date/time format string.
Example: If user try to run the following SQL statement
select to_char(SYSDATE, 'DD-MON-YYYY HH24:MI:SS') "Current Date Time" from dual
A popup dialog prompts for data input, if user press either OK or Cancel button, the result data is shown as below.
Current Date Time
-------------------------------------
14-MAY-2010 16&05&33
Known Bugs in MyOra 2.0.0
- Explain Plan - If any statement references a table in its own schema without user qualification, the Explain Plan is not visible for a different login user.
- DB Activity - If Oracle System Statistics value (from the database) is greater than 2^31, then the Statistics value on the screen is shown as zero.
- In correct JDBC URL in MyOra Help Page and User Guide (PDF file) -
The JDBC URL login connection string was printed incorrectly (a typing error).
Correct format for JDBC URL is jdbc:oracle:thin:@
- If to_date function in prompt mode is used in any SQL statement (select, update, insert, delete) results in a sql syntax error.
to_date(:1, 'DD-MON-YYYY HH24:MI:SS')
Copyright © Jayam Systems, LLC
