Updates 47003 » History » Version 2
Version 1 (Pierre Marc, 06/04/2012 09:44 AM) → Version 2/3 (Pierre Marc, 06/04/2012 09:45 AM)
h1. 4.7.003 Updates
h2. Bugs
* The When some java code calls some java code threw Nirva (ex java procedure calls a java procedure) and the last calling code get something from the output buffer that is greater than 1024 bytes, a potentially fatal exception management changed in occurs. Nirva becomes instable and may crash. (bug #61).
* When the 4.7.001 version under linux. We added import file contains a compilation option allowing to throw line with length greater than the specified maximum line length (so terminating with an exception when antislash), the import adds a signal occurs. This space in the data before reading the next line. (bug #60).
* The LINE_LENGHT parameter of the EXPORT command is not working when fine with a value greater than 1024. (bug #59).
* The command OBJECT:TABLE_CLEAR_ROWS removes the jvm is beeing used because rows instead of clearing them. This occurs in both nvs (server) and nvc (client). (bug #58).
* The OBJECT:TABLE_CLEAR_ROW removes the jvm has its own exception management that is not compatible. given row instead of clearing it. (bug #62). #57).
h2. Features
* Adding an exception and signal log.
h2. Bugs
* The When some java code calls some java code threw Nirva (ex java procedure calls a java procedure) and the last calling code get something from the output buffer that is greater than 1024 bytes, a potentially fatal exception management changed in occurs. Nirva becomes instable and may crash. (bug #61).
* When the 4.7.001 version under linux. We added import file contains a compilation option allowing to throw line with length greater than the specified maximum line length (so terminating with an exception when antislash), the import adds a signal occurs. This space in the data before reading the next line. (bug #60).
* The LINE_LENGHT parameter of the EXPORT command is not working when fine with a value greater than 1024. (bug #59).
* The command OBJECT:TABLE_CLEAR_ROWS removes the jvm is beeing used because rows instead of clearing them. This occurs in both nvs (server) and nvc (client). (bug #58).
* The OBJECT:TABLE_CLEAR_ROW removes the jvm has its own exception management that is not compatible. given row instead of clearing it. (bug #62). #57).
h2. Features
* Adding an exception and signal log.