|
| | __init__ (self, args=None, **kwargs) |
| |
| | close (self) |
| | Rewrites out everything to SQL schema file, ensuring all source metas.
|
| |
| | emit (self, topic, msg, stamp=None, match=None, index=None) |
| | Writes out message type CREATE TABLE statements to SQL schema file.
|
| |
| | validate (self) |
| | Returns whether "dialect" and "nesting" and "overwrite" parameters contain supported values and file is writable.
|
| |
| | __init__ (self, args=None, **kwargs) |
| |
| | __enter__ (self) |
| | Context manager entry.
|
| |
| | __exit__ (self, exc_type, exc_value, traceback) |
| | Context manager exit, closes sink.
|
| |
| | autodetect (cls, target) |
| | Returns true if target is recognizable as output for this sink class.
|
| |
| | bind (self, source) |
| | Attaches source to sink.
|
| |
| | close (self) |
| | Shuts down output, closing any files or connections.
|
| |
| | configure (self, args=None, **kwargs) |
| | Updates sink configuration.
|
| |
| | emit (self, topic, msg, stamp=None, match=None, index=None) |
| | Outputs ROS message.
|
| |
| | emit_meta (self) |
| | Outputs source metainfo like bag header as debug stream, if not already emitted.
|
| |
| | flush (self) |
| | Writes out any pending data to disk.
|
| |
| | is_highlighting (self) |
| | Returns whether this sink requires highlighted matches.
|
| |
| | thread_excepthook (self, text, exc) |
| | Handles exception, used by background threads.
|
| |
| | validate (self) |
| | Returns whether sink prerequisites are met (like ROS environment set if LiveSink).
|
| |
| | __init__ (self, args=None, **kwargs) |
| |
| | close (self) |
| | Clears data structures.
|
| |
| | validate (self) |
| | Returns whether arguments are valid.
|
| |
Writes SQL schema file for message type tables and topic views.
Output will have:
table "pkg/MsgType" for each topic message type, with ordinary columns for scalar fields, and structured columns for list fields; plus underscore-prefixed fields for metadata, like _topic as the topic name.
If launched with nesting-option, tables will also be created for each nested message type.
- view "/full/topic/name" for each topic, selecting from the message type table
Definition at line 43 of file sql.py.