https://sourceforge.net/p/dboutputter4rs/wiki/Implementation/Recent changes to ImplementationenThu, 24 Jan 2013 23:41:02 -0000https://sourceforge.net/p/dboutputter4rs/wiki/Implementation/<div class="markdown_content"><pre>--- v1 +++ v2 @@ -4,31 +4,41 @@ DefaultDBOutputter ------------------ -extends and uses most of the functionality. To enable chaching, -overwrites and stores all sql statements into a buffer until the limit -is reached. Furthermore, it adds the column definitions as the first -part of SQL statement. To flush the buffer on , also overwrites and -directly calls to by-pass caching. +**DefaultDBOutputter.** **CachedJdbcAppender** extends **JDBCAppender** +and uses most of the functionality. To enable chaching, +**DefaultDBOutputter.** **CachedJdbcAppender** overwrites +**JDBCAppender#execute()** and stores all sql statements into a buffer +until the limit is reached. Furthermore, it adds the column definitions +as the first part of SQL statement. To flush the buffer on **close()**, +**DefaultDBOutputter.** **CachedJdbcAppender** also overwrites +**JDBCAppender#close()** and directly calls **JDBCAppender#execute()** +to by-pass caching. -Overwriting is used to generate the SQL peace for every column defined -in the and also adds the if activated. +Overwriting **JDBCAppender\#getLogStatement()** is used to generate the +SQL peace for every column defined in the **DbOutputterDescriptor.** +**CachedJdbcAppender** and also adds the **runID** if activated. -To ensure all cache is sent to the database, the ’s method is scheduled -at the last tick with priority . Otherwise, is not called before the +To ensure all cache is sent to the database, the +**DbOutputterDescriptor.** **CachedJdbcAppender**’s **close()** method +is scheduled at the last tick with priority **ScheduleParameters.** +**LAST_PRIORITY**. Otherwise, **close()** is not called before the simualtion is reset, and in case the user closes the application without resetting the cached data is missed. Error Handling -------------- -The plugin does not throw in order not to interrupt simulations because -of output errors. Instead, a ERROR-Logging to the Repast Simphony -Message Center is triggered. +The plugin does not throw **SQLExceptions** in order not to interrupt +simulations because of output errors. Instead, a ERROR-Logging to the +Repast Simphony Message Center is triggered. Run Information Handling ------------------------ Since Repast Simphony 2.0.0, initialisation of data outputters take -place not before the first data is logged. Therefore, calls to before -the first data is logged cannot access any information required to -connect to the database. That’s why was added. +place not before the first data is logged. Therefore, calls to +**DefaultDBOutputter.getCurrentMaxRunId()** before the first data is +logged cannot access any information required to connect to the +database. That’s why +**DefaultDBOutputter.getCurrentMaxRunId(runInfoTable, dbConInfo)** was +added. </pre> </div>HolzhauerThu, 24 Jan 2013 23:41:02 -0000https://sourceforge.net34b3952810281ee015ae94126c0618d3e1d7f8aehttps://sourceforge.net/p/dboutputter4rs/wiki/Implementation/<div class="markdown_content"><h1 id="implementation">Implementation</h1> <h2 id="defaultdboutputter">DefaultDBOutputter</h2> <p>extends and uses most of the functionality. To enable chaching,<br /> overwrites and stores all sql statements into a buffer until the limit<br /> is reached. Furthermore, it adds the column definitions as the first<br /> part of SQL statement. To flush the buffer on , also overwrites and<br /> directly calls to by-pass caching.</p> <p>Overwriting is used to generate the SQL peace for every column defined<br /> in the and also adds the if activated.</p> <p>To ensure all cache is sent to the database, the ’s method is scheduled<br /> at the last tick with priority . Otherwise, is not called before the<br /> simualtion is reset, and in case the user closes the application without<br /> resetting the cached data is missed.</p> <h2 id="error-handling">Error Handling</h2> <p>The plugin does not throw in order not to interrupt simulations because<br /> of output errors. Instead, a ERROR-Logging to the Repast Simphony<br /> Message Center is triggered.</p> <h2 id="run-information-handling">Run Information Handling</h2> <p>Since Repast Simphony 2.0.0, initialisation of data outputters take<br /> place not before the first data is logged. Therefore, calls to before<br /> the first data is logged cannot access any information required to<br /> connect to the database. That’s why was added.</p></div>HolzhauerThu, 24 Jan 2013 16:40:18 -0000https://sourceforge.netf0e8a5baee035d66c178a9c12de4910cca406267