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
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
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
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
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
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
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
On 19 Jan 2017, at 5:55pm, Scott Hess wrote:
> You could use sqlite3_exec(), which is internally just going to issue
> multiple single SQL statements.
Just to clarify, dealing with lists of commands is exactly what sqlite3_exec()
is intended to do. It should do exactly what
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.
Seems like I'm pretty much stuck with the issue.
On Thu, Jan 19, 2017 at 4:00 AM <
sqlite-users-requ...@mailinglists.sqlite.org> wrote:
>
On Thu, Jan 19, 2017 at 9:24 AM, Igor Korot wrote:
> Is it possible to write something like this:
>
> sqlite3_prepare_v2( m_db, "BEGIN TRANSACTION; CREATE TEMP TABLE temp
> AS SELECT * FROM mytable; DROP TABLE mytable; CREATE TABLE mytable(id
> INTEGER PRIMARY KEY, name TEXT
Igor Korot wrote:
> sqlite3_prepare_v2( m_db, "BEGIN TRANSACTION; CREATE TEMP TABLE temp
> AS SELECT * FROM mytable; DROP TABLE mytable; CREATE TABLE mytable(id
> INTEGER PRIMARY KEY, name TEXT PRIMARY KEY, salary INTEGER); INSERT
> INTO mytable SELECT * FROM temp; DROP TABLE temp; COMMIT;", -1, ,
Hi, ALL,
Is it possible to write something like this:
sqlite3_prepare_v2( m_db, "BEGIN TRANSACTION; CREATE TEMP TABLE temp
AS SELECT * FROM mytable; DROP TABLE mytable; CREATE TABLE mytable(id
INTEGER PRIMARY KEY, name TEXT PRIMARY KEY, salary INTEGER); INSERT
INTO mytable SELECT * FROM temp;
12 matches
Mail list logo