Skip to content

clarification on "Limitations and caveats" #451

@justinmk

Description

@justinmk

Is the Limitations and caveats section of the readme outdated?

The current implementation caches this information in a ConcurrentDictionary object. The objects it stores are never flushed.

8ed5f61 added automatic GC.

If you are generating SQL strings on the fly without using parameters it is possible you will hit memory issues.

Does 8747316 have implications for that statement?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions