Uploaded image for project: 'Couchbase Lite'
  1. Couchbase Lite
  2. CBL-71

LiteCore database alias clashes with select all alias

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 2.6.0
    • 2.6.0
    • Java-Android
    • Security Level: Public

    Description

      When doing a select all from as query, the db alias and result alias end up being the same and causing a duplicate alias error.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          blake.meike Blake Meike added a comment -

          Jay Vavachan Definitely.  Can you make a new ticket, for this, against CBL-Lite/Java-Android?

          blake.meike Blake Meike added a comment - Jay Vavachan Definitely.  Can you make a new ticket, for this, against CBL-Lite/Java-Android?
          blake.meike Blake Meike added a comment -

          Well... that's not a new ticket... Thanks.

          blake.meike Blake Meike added a comment - Well... that's not a new ticket... Thanks.
          jimb Jim Borden added a comment -

          I'm against making multiple tickets for different CBL variants. That is the purpose of the components field. iOS should stay in the components though since it was originally affected. If Android is not affected the component can be removed and the ticket can be closed.

          jimb Jim Borden added a comment - I'm against making multiple tickets for different CBL variants. That is the purpose of the components field. iOS should stay in the components though since it was originally affected. If Android is not affected the component can be removed and the ticket can be closed.
          blake.meike Blake Meike added a comment -

          Multiple components seems like one way to do this.  I would favor doing the way that, e.g. Doc does it: one master ticket for the issue, and sub-tasks for each of the components.

          The advantage of that is that it is easy to track what has been done and what hasn't.  If we just use multiple components, we, what? wait until the last component has been removed from the ticket?

          I admit that 5 tickets where 1 might do is noticeable overhead.  I personally think it is worth it.  I could be convinced otherwise.  It is a discussion we should have.

          blake.meike Blake Meike added a comment - Multiple components seems like one way to do this.  I would favor doing the way that, e.g. Doc does it: one master ticket for the issue, and sub-tasks for each of the components. The advantage of that is that it is easy to track what has been done and what hasn't.  If we just use multiple components, we, what? wait until the last component has been removed from the ticket? I admit that 5 tickets where 1 might do is noticeable overhead.  I personally think it is worth it.  I could be convinced otherwise.  It is a discussion we should have.
          blake.meike Blake Meike added a comment -

          Verified

          blake.meike Blake Meike added a comment - Verified

          People

            blake.meike Blake Meike
            jimb Jim Borden
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty