Thanks to all for the input. To clarify, yes the ORDER BY clause is in the
view definition and the SELECT statement that addresses the view does not
have an ORDER BY clause.
I think the penny has finally dropped for me on this issue. The key was
the description by a responder that views are not
Loved that explanation. I could easily understand it.
On Jan 19, 2017 17:14, "James K. Lowden" wrote:
> On Wed, 18 Jan 2017 23:36:14 +
> Peter Haworth wrote:
>
> > if I include a WHERE claus, the view's ORDER BY clause is ignored and
> > the rows are returned in seemingly random order.
> >
On Wed, 18 Jan 2017 23:36:14 +
Peter Haworth wrote:
> if I include a WHERE claus, the view's ORDER BY clause is ignored and
> the rows are returned in seemingly random order.
>
> Searching around the web suggests that this behavior is accepted as
> correct in mySQL although I haven't been ab
On Thu, Jan 19, 2017 at 1:03 PM, R Smith wrote:
> On 2017/01/19 9:01 PM, Simon Slavin wrote:
>> On 19 Jan 2017, at 6:54pm, Scott Hess wrote:
>>> Just to be clear, you're saying that the VIEW has an ORDER BY, but
>>> when you SELECT from the VIEW you aren't using an ORDER BY?
>>>
>>> If your outer
On 2017/01/19 9:01 PM, Simon Slavin wrote:
On 19 Jan 2017, at 6:54pm, Scott Hess wrote:
Just to be clear, you're saying that the VIEW has an ORDER BY, but
when you SELECT from the VIEW you aren't using an ORDER BY?
If your outer SELECT is using an ORDER BY and that is not respected,
that se
On 19 Jan 2017, at 6:54pm, Scott Hess wrote:
> Just to be clear, you're saying that the VIEW has an ORDER BY, but
> when you SELECT from the VIEW you aren't using an ORDER BY?
>
> If your outer SELECT is using an ORDER BY and that is not respected,
> that seems like an egregious bug. But if yo
On Wed, Jan 18, 2017 at 3:36 PM, Peter Haworth wrote:
> I am in the process of converting an SQLite database to mySQL. The SQLIte
> db includes several views with ORDER BY clauses that have always returned
> qualifying rows in the correct order.
>
> I am discovering that in mySQL issuing a SELECT
On 19 Jan 2017, at 5:58pm, Peter Haworth wrote:
> Thanks Simon. According to SHOW VARIABLES LIKE "@version@" inno-db version
> is 5.6.25 and version is 5.6.25-log, which I think are pretty recent
> versions.
Those are far more recent than the versions I know had those related problems.
Given
--
>
> Message: 1
> Date: Wed, 18 Jan 2017 23:36:14 +0000
> From: Peter Haworth
> To: sqlite-users@mailinglists.sqlite.org
> Subject: [sqlite] [OT] mySQL ORDER BY clause in Views
> Message-ID:
> wgsvwwapzkee45bhak...@mail.gmail.com>
> Content-Type: t
On 18 Jan 2017, at 11:36pm, Peter Haworth wrote:
> I am discovering that in mySQL issuing a SELECT statement against these
> same views works fine in terms of the order in which the rows are returned
> if the SELECT does not include a WHERE clause but if I include a WHERE
> claus, the view's ORD
I am in the process of converting an SQLite database to mySQL. The SQLIte
db includes several views with ORDER BY clauses that have always returned
qualifying rows in the correct order.
I am discovering that in mySQL issuing a SELECT statement against these
same views works fine in terms of the o
11 matches
Mail list logo