Back to bug 37167
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| pmladek | 2011-05-23 12:07:36 UTC | CC | nopower | |
| bjoern.michaelsen | 2011-12-23 12:01:37 UTC | Status | NEW | NEEDINFO |
| iplaw67 | 2012-03-01 00:29:17 UTC | CC | iplaw67 | |
| reisi007 | 2012-08-14 14:01:24 UTC | Status | NEEDINFO | RESOLVED |
| CC | reisi007 | |||
| Resolution | --- | INVALID | ||
| iplaw67 | 2012-08-15 07:13:16 UTC | Status | RESOLVED | UNCONFIRMED |
| Resolution | INVALID | --- | ||
| Ever confirmed | 1 | 0 | ||
| iplaw67 | 2012-08-15 07:18:44 UTC | Status | UNCONFIRMED | NEW |
| Ever confirmed | 0 | 1 | ||
| iplaw67 | 2012-08-15 08:13:54 UTC | OS | Windows (All) | All |
| iplaw67 | 2012-08-15 09:41:18 UTC | Hardware | x86 (IA32) | All |
| reisi007 | 2012-08-15 11:24:32 UTC | CC | reisi007 | |
| iplaw67 | 2012-08-15 20:51:28 UTC | Component | BASIC | Database |
| dr | 2012-09-05 07:56:49 UTC | CC | dr | |
| serval2412 | 2013-12-31 16:44:37 UTC | CC | serval2412 | |
| serval2412 | 2013-12-31 17:40:28 UTC | CC | lionel | |
| lionel | 2014-01-06 15:07:20 UTC | Status | NEW | ASSIGNED |
| Assignee | libreoffice-bugs | lionel | ||
| lionel | 2014-01-06 15:49:12 UTC | Summary | Null pointer exception while executing a prepared statement | Null pointer exception when executing a prepared statement with no arguments |
| libreoffice-commits | 2014-01-06 16:11:34 UTC | Whiteboard | target:4.3.0 | |
| lionel | 2014-01-06 16:21:11 UTC | Status | ASSIGNED | RESOLVED |
| Resolution | --- | FIXED | ||
| lionel | 2014-01-07 11:05:45 UTC | Summary | Null pointer exception when executing a prepared statement with no arguments | JDBC/HSQLDB: Null pointer exception when executing a prepared statement with no arguments |
| libreoffice-commits | 2014-01-08 15:18:55 UTC | Whiteboard | target:4.3.0 | target:4.3.0 target:4.1.5 |
| libreoffice-commits | 2014-01-08 15:20:13 UTC | Whiteboard | target:4.3.0 target:4.1.5 | target:4.3.0 target:4.1.5 target:4.2.1 |
Back to bug 37167
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.