crash on Windows when < in topic name

[rkuhn]

Node exited with error InternalError(Component Swarm

Caused by:
    0: unable to open database file: C:\Program Files\Actyx\Node\actyx-data\store\default-topic-635687454154sdyy<sdfg-blobs.sqlite
    1: Error code 14: Unable to open the database file)

Windows file name rules

Use any character in the current code page for a name, including Unicode characters and characters in the extended character set (128–255), except for the following:

• The following reserved characters:

  < (less than)
  > (greater than)
  : (colon)
  " (double quote)
  / (forward slash)
  \ (backslash)
  | (vertical bar or pipe)
  ? (question mark)
  * (asterisk)
  Integer value zero, sometimes referred to as the ASCII NUL character.

• Characters whose integer representations are in the range from 1 through 31, except for alternate data streams where these characters are allowed. For more information about file streams, see File Streams.

• Any other character that the target file system does not allow.

Do not use the following reserved names for the name of a file:

• CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9. Also avoid these names followed immediately by an extension; for example, NUL.txt is not recommended.

Do not end a file or directory name with a space or a period.

Maximum length of the file path is 260 characters.

[rkuhn]

This probably requires a new DB version with associated migration of filenames. Unix-like systems strictly speaking also need such a facility, as \x00 and / are forbidden in filenames.

[rkuhn]

Or we could just change the settings schema to forbid such characters. Would require rethinking the startup a bit so that users can usefully be informed and get a chance to fix the settings.