Skip to content

Enforce separation of concerns from keyspace creation #3

Description

@indexzero

#2 broke the separation of concerns between Datastar instances and CQL. I would suggest that the CQL for keyspace creation go into lib/statement-builder/statements/create-keyspace.js which is then instantiated and invoked directly in Datastar.connect.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions