Hi again,
I know the focus of SQLite people on "size", and "testing". Wouldn't a basic implementation of CTE in fact : - help the "size" of the global embedded system to be smaller ? - without impacting the "testing" ? Indeed, a "simple" implementation of CTE : * could rely only on SQLite internal functionalities that are already available : . don't change the motor, . just translate the sql. * would not require lots of work on development and testing : . sql start by "with " => pre-translate, . sql does not start by "with " => do business as usual. * would decrease the size of the GLOBAL embedded system (SQLite+Application) : . less calls (and characters) to generate from the Applicatin towards SQLite to create/delete those views _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users