Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
1.0.0
-
None
Description
This can cause all sorts of disasters on Windows (at least) debug and release are mixed, but also theoretically possible if different VS versions are used for build of the connector and application(not confirmed atm).
Currently connector has std::map in connect() methods, std::istream in set/getBlob(std::istream is probably safe to use, though)
These classes(that should substitute aforementioned use of STL classes) implementations should hide from application underlying classes implementations in the way similar to how SQLString hides use of std::string
Attachments
Issue Links
- includes
-
CONCPP-85 SQLString constructor from std::string should not be exported
- Closed