Skip to content

JAVA-1227: Document "SELECT *" issue with prepared statement#703

Merged
olim7t merged 1 commit into
3.0.xfrom
java1227
Jul 5, 2016
Merged

JAVA-1227: Document "SELECT *" issue with prepared statement#703
olim7t merged 1 commit into
3.0.xfrom
java1227

Conversation

@tolbertam

@tolbertam tolbertam commented Jun 30, 2016

Copy link
Copy Markdown
Contributor

For JAVA-1227.

Added section to 'Prepared Statements' doc and FAQ. The first paragraph is the same in each section, with the FAQ entry linking to the doc.

Assigned to 3.0.3 milestone as the jira ticket targets this.

@tolbertam tolbertam added this to the 3.0.3 milestone Jun 30, 2016
@tolbertam tolbertam force-pushed the java1227 branch 3 times, most recently from af2db15 to 2a528f8 Compare June 30, 2016 16:22

Therefore it is currently recommended to not create prepared statements
for 'select *' queries unless you don't plan on making schema changes involving
adding or dropping columns. Alternatively you should list all columns of interest

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would replace "unless you don't plan" with "if you plan" (the double negative is harder to read).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think I should not fix this :P (fixing shortly)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 609f3a2, can be squashed before merge.

@olim7t

olim7t commented Jun 30, 2016

Copy link
Copy Markdown
Contributor

👍

Comment thread faq/README.md Outdated
```


### Why do my 'select *' `PreparedStatement`-based queries stop working after a schema change?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that we tend to use upper case letters for CQL keywords throughout the manual, so for consistency I suggest changing 'select *' to SELECT *.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Always good to be consistent, will fix.

@olim7t olim7t merged commit c9381d1 into 3.0.x Jul 5, 2016
@olim7t olim7t deleted the java1227 branch July 5, 2016 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants