Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
1
-
SDK1: GA and Priority List
Description
As I understand it, the 'SDK3' way to query would be something like:
cluster.query('SELECT * FROM `default`') # which works fine |
# or
|
cluster.query('SELECT * FROM `default` WHERE foo LIKE $email', email='%foo%'). # nope |
# or
|
cluster.query('SELECT * FROM `default` WHERE foo LIKE $1', '%foo%') # nope |
But the older way, using a N1QLQuery object, works fine:
cluster.query(N1QLQuery('SELECT * FROM `default` WHERE email LIKE $email', email='%king%')) |
A couple questions arise:
- do we really want to still support a N1QLQuery object?
- should we support something like the 2 usages above?
Of course it is entirely possible I'm misunderstanding the code (or the sdk3 RFCs).
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
As I understand it, the 'SDK3' way to query would be something like:
{code:python}cluster.query('SELECT * FROM `default`') // which works fine # or cluster.query('SELECT * FROM `default` WHERE foo LIKE $email', email='%foo%'). // nope # or cluster.query('SELECT * FROM `default` WHERE foo LIKE $1', '%foo%') // nope {code} But the older way, using a N1QLQuery object, works fine: {code:python}cluster.query(N1QLQuery('SELECT * FROM `default` WHERE email LIKE $email', email='%king%')) {code} A couple questions arise: * do we really want to still support a N1QLQuery object? * should we support something like the 2 usages above? Of course it is entirely possible I'm misunderstanding the code (or the sdk3 RFCs). |
As I understand it, the 'SDK3' way to query would be something like:
{code:python}cluster.query('SELECT * FROM `default`') # which works fine # or cluster.query('SELECT * FROM `default` WHERE foo LIKE $email', email='%foo%'). # nope # or cluster.query('SELECT * FROM `default` WHERE foo LIKE $1', '%foo%') # nope {code} But the older way, using a N1QLQuery object, works fine: {code:python}cluster.query(N1QLQuery('SELECT * FROM `default` WHERE email LIKE $email', email='%king%')) {code} A couple questions arise: * do we really want to still support a N1QLQuery object? * should we support something like the 2 usages above? Of course it is entirely possible I'm misunderstanding the code (or the sdk3 RFCs). |
| Status | New [ 10003 ] | Open [ 1 ] |
| Fix Version/s | 3.0.0-beta.3 [ 16328 ] |
| Fix Version/s | 3.0.0-beta.2 [ 16505 ] | |
| Fix Version/s | 3.0.0-beta.3 [ 16328 ] |
| Fix Version/s | 3.0.0-beta.3 [ 16328 ] | |
| Fix Version/s | 3.0.0-beta.2 [ 16505 ] |
| Sprint | SDK1: GA and Priority List [ 959 ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Assignee | Ellis Breen [ ellis.breen ] | David Kelly [ david.kelly ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Story Points | 1 |
| Workflow | Couchbase SDK Workflow [ 155225 ] | Couchbase SDK Workflow with Review [ 257260 ] |