Hi Matija, I just wish to know if there are any disadvantages when using prepared statement or any warning signs I should look for. Queries will run multiple times so it fits the use case.
Thanks! Shalom Sagges DBA <http://www.linkedin.com/company/164748> <http://twitter.com/liveperson> <http://www.facebook.com/LivePersonInc> We Create Meaningful Connections On Tue, Aug 29, 2017 at 2:18 PM, Matija Gobec <matija0...@gmail.com> wrote: > Do you have any concrete questions re prepared statements? > > They are faster to execute since the statement is already parsed and in C* > and you just pass the parameters. No additional statement processing is > needed. > > Matija > > On Tue, Aug 29, 2017 at 12:33 PM, Shalom Sagges <shal...@liveperson.com> > wrote: > >> Insights, anyone? >> >> >> Shalom Sagges >> DBA >> <http://www.linkedin.com/company/164748> <http://twitter.com/liveperson> >> <http://www.facebook.com/LivePersonInc> We Create Meaningful Connections >> >> >> >> On Mon, Aug 28, 2017 at 10:43 AM, Shalom Sagges <shal...@liveperson.com> >> wrote: >> >>> Hi Everyone, >>> >>> I want to start working with Prepared Statements. >>> >>> I've read https://docs.datastax.com/en/developer/java-driver/3.1/ >>> manual/statements/prepared/ and just wanted to know if there are any >>> other considerations I need to take into account when deciding to use >>> Prepared Statements. >>> >>> Thanks! >>> >>> >>> Shalom Sagges >>> DBA >>> <http://www.linkedin.com/company/164748> <http://twitter.com/liveperson> >>> <http://www.facebook.com/LivePersonInc> We Create Meaningful Connections >>> >>> >>> >> >> >> This message may contain confidential and/or privileged information. >> If you are not the addressee or authorized to receive this on behalf of >> the addressee you must not use, copy, disclose or take action based on this >> message or any information herein. >> If you have received this message in error, please advise the sender >> immediately by reply email and delete this message. Thank you. >> > > -- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you.
