| ID | Date | Author  | Topic | Subject | Text |  | 
| 1276 | 22 Apr 2017 | Konstantin Olchanski | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | > > Fixed a small buglet, now saving and reloading odb in the old ".odb" format will silently
 truncate all overlong strings to 256 bytes.
 |  | 
| 1277 | 22 Apr 2017 | Konstantin Olchanski | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | > ODB name lengths (the name of a key) are limited to 256 characters, the length of
 strings in the ODB should NOT be limited.
 |  | 
| 1280 | 26 Apr 2017 | Konstantin Olchanski | Info | added db_get_value_string() | Since we have been regularly running into problems with db_get_xxx(TID_STRING) and
 string buffers of mismatched size,
 |  | 
| 1284 | 02 May 2017 | Konstantin Olchanski | Info | added db_resize_string() | > Since we have been regularly running into problems with db_get_xxx(TID_STRING) and
 string buffers of mismatched size,
 |  | 
| 1285 | 02 May 2017 | Konstantin Olchanski | Bug Report | mhttpd inline-editor and web MAX_STRING_LENGTH, stop form odbedit broken | > > I shall check on the use of MAX_STRING_LENGTH at least in odb itself...
 
 |  | 
| 1286 | 02 May 2017 | Konstantin Olchanski | Info | mhttpd inline-editor change | I changed the mhttpd odb inline editor to use the json-rpc interface. Good things:
 
 |  | 
| 1287 | 02 May 2017 | Konstantin Olchanski | Forum | Problem with logger at run start | > Wed Apr 26 23:03:12 2017 [mhttpd,ERROR] [midas.c:9106:rpc_client_connect,ERROR] cannot
 connect to host "scar
 |  | 
| 1288 | 02 May 2017 | Konstantin Olchanski | Bug Report | run start/stop oddity | I should really get around to fix this junk
 error message:
 |  | 
| 1289 | 02 May 2017 | Konstantin Olchanski | Info | added db_get_value_string() | > Just some thought for discussion: 
 Even more thoughts:
 |  | 
| 1292 | 16 May 2017 | Konstantin Olchanski | Bug Report | mhttpd / history / export data | > A handy feature of the history of the mhttpd is to export the data. However, this
 > seems to be broken. It currently only works
 |  | 
| 1293 | 16 May 2017 | Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | Suddenly the mhttpd odb inline editor is truncating the odb string entries to the actual length
 of the
 |  | 
| 1294 | 31 May 2017 | Konstantin Olchanski | Info | modified db_watch() arguments | for reasons unknown, db_watch() did not have an "info" parameter passed through to the
 callback
 |  | 
| 1295 | 31 May 2017 | Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > What a mess. 
 The mess with db_get_record() and db_open_record()
 |  | 
| 1296 | 31 May 2017 | Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > 2) replace all uses of db_open_record(MODE_READ) with db_watch() in conjunction with db_get_record1().
 
 |  | 
| 1298 | 06 Jun 2017 | Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > Done to all in-tree programs, except for mana.c (not using it), sequencer.cxx (cannot
 test it) and a few places where watching
 |  | 
| 1299 | 06 Jun 2017 | Konstantin Olchanski | Bug Report | MAX_STRING_LENGTH, stop form odbedit broken | > ... the xml reader, probably has same problem > ... xml writer truncates long strings via
 truncation in db_sprintf()
 |  | 
| 1305 | 13 Jul 2017 | Konstantin Olchanski | Info | implemented: json-rpc batch requests | The mhttpd json-rpc interface now implements batch requests per
 http://www.jsonrpc.org/specification#batch
 |  | 
| 1310 | 04 Aug 2017 | Konstantin Olchanski | Info | Notes on installing midas from scratch | Notes on installing midas from scratch. The instruction on midaswiki will be synced with
 this later.
 |  | 
| 1313 | 12 Aug 2017 | Konstantin Olchanski | Suggestion | Increasing Max Number of Frontends | The checks for byte sizes of critical data structures have been added to ensure (enforce)
 binary compatibility
 |  | 
| 1315 | 13 Aug 2017 | Konstantin Olchanski | Suggestion | Increasing Max Number of Frontends | > if (sizeof(INT) != 4) then severe_error_and_stop_all_programs() 
 Quick reply.
 |  |