[GitHub] ignite pull request #1062: Ignite 3791 Wrap keyspace, table and column name ...

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1062: Ignite 3791 Wrap keyspace, table and column name ...

andrey-kuznetsov
GitHub user irudyak opened a pull request:

    https://github.com/apache/ignite/pull/1062

    Ignite 3791 Wrap keyspace, table and column name with escape characters in generated CQL queries

   

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/irudyak/ignite ignite-3791

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1062.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1062
   
----
commit f38a14defd0f1ebd41e0f49ef19f44902d1780d0
Author: Igor <[hidden email]>
Date:   2016-09-14T23:01:11Z

    printing index DDL statements if there are any indexes registered for a table

commit 27e551fe10a9577d63ebb9e6849aba1de1e5def3
Author: Igor <[hidden email]>
Date:   2016-09-14T23:02:22Z

    wrapped table name, keyspace name and column names with double quotes in all generated DDL/DML statements

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1062: IGNITE 3791 Wrap keyspace, table and column name ...

andrey-kuznetsov
Github user irudyak closed the pull request at:

    https://github.com/apache/ignite/pull/1062


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1062: IGNITE 3791 Wrap keyspace, table and column name ...

andrey-kuznetsov
In reply to this post by andrey-kuznetsov
GitHub user irudyak reopened a pull request:

    https://github.com/apache/ignite/pull/1062

    IGNITE 3791 Wrap keyspace, table and column name with escape characters in generated CQL queries

   

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/irudyak/ignite ignite-3791

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1062.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1062
   
----
commit f38a14defd0f1ebd41e0f49ef19f44902d1780d0
Author: Igor <[hidden email]>
Date:   2016-09-14T23:01:11Z

    printing index DDL statements if there are any indexes registered for a table

commit 27e551fe10a9577d63ebb9e6849aba1de1e5def3
Author: Igor <[hidden email]>
Date:   2016-09-14T23:02:22Z

    wrapped table name, keyspace name and column names with double quotes in all generated DDL/DML statements

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1062: IGNITE 3791 Wrap keyspace, table and column name ...

andrey-kuznetsov
In reply to this post by andrey-kuznetsov
Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/1062


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---