On Wed, Jun 5, 2013 at 12:02 PM, Dominique Devienne <[email protected]>wrote:
> But that brings up the question about why the create view itself does not
> fail?
>
> C:\Users\DDevienne>sqlite3
> SQLite version 3.7.15.2 2013-01-09 11:53:05
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> create table a (b int primary key, c);
> sqlite> create table d (e int primary key, f, g);
> sqlite> create view v as select * from a union all select * from d;
>
FWIW, the statements above fails on create view in Oracle (see below).
Could SQLite3 similarly fail "early" on the view creation?
If not, what's the rationale for not doing so?
Thanks, --DD
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
SQL> create table a (b integer primary key, c char);
Table created.
SQL> create table d (e integer primary key, f char, g char);
Table created.
SQL> create view v as select * from a union all select * from d;
create view v as select * from a union all select * from d
*
ERROR at line 1:
ORA-01789: query block has incorrect number of result columns
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
