Back to Known Issues PageBack

DCPS Known Issues

Report ID. Description
dds184 Query parser doesn't support escape characters
The internal OpenSplice DDS query parser does not support escape characters. This implicates that specific tokens cannot be used in query expressions (like for instance SQL keywords 'select', 'where', etc).
Impact at API level:
  • Topics with a SQL keyword as name cannot be created
  • QueryCondition expressions cannot refer to datafields with SQL keyword as name
  • ContentFilteredTopic expressions cannot refer to datafields with SQL keyword as name
4508
dds206 		typeSupport with invalid type name causes crash during register_type
When a type support object is created with an type name which is not known in the meta database, the following register_type function crashes.
dds492 idlpp cannot handle same struct in a struct or forward declarations to structs
The following (faulty) idl code generates a 'floating point exception', instead idlpp should not allow such constructs. 

            struct TestStruct;

            struct TestStruct{
                long x;
                TestStruct someEnum;
                string val;
            };
The following idl also fails (the forward declaration to the TestStruct is not correctly processed): 

            struct TestStruct;

            struct TestStruct1{
                TestStruct y;
            };

            struct TestStruct{
                long x;
            };
with the error: ***DDS parse error TestStruct undefined at line: 4. The following idl construct is not allowed, however the IDL preprocessor does not give a clear error: 

            struct TestStruct;

            struct TestStruct1{
                TestStruct y;
            };

            struct TestStruct{
                TestStruct1 x;
            };
4821
dds494 		SQL RelOp like not supported
Using the SQL relational operator like is not supported.
dds1696 Limitations for output directories for ospl_projgen on Integrity
ospl_projgen will generate projects which will build incorrectly if it is supplied an output directory ( -o option ) in which the final part of the path matches the name of one of the address spaces being generated.
e.g. ospl_projgen ... -t mmstat -o path/mmstat
These projects appear to build correctly however the final image will be incorrect.
Other names to avoid currently are inetserver, ivfs_server, ResourceStore, spliced, networking, durability, pong, ping1, ping2, ping3, ping4, ping5, ping6, shmdump, Chatter, Chatter_Quit, MessageBoard, UserLoad
dds1711 Warnings when compiling with the Studio12 compiler
There are still numerous warnings when using the Studio12 compiler. These can be ignored and will be tidied in future releases.

PrismTech TOP
Top