tree 6fc754cddef092472aeaf57067150cb2e31b1471
parent 3caae9ef9f4af29c2309ced052f62a40dd5d4058
author RamanGrover29@gmail.com <RamanGrover29@gmail.com@eaa15691-b419-025a-1212-ee371bd00084> 1352420865 +0000
committer RamanGrover29@gmail.com <RamanGrover29@gmail.com@eaa15691-b419-025a-1212-ee371bd00084> 1352420865 +0000

Merged asterix_statement_model_fix into asterix_stabilization
1) Asterix now has a revised statement model. 
  a) Each statement (definition includes a query) is executed as an independent transaction.
  b) Statements are executed in the order of submission with no implicit re-orderings.
  c) Asterix does not differentiate between DDL and DML statements. This is unlike the previous model which executed DDL statements prior to DML statements.
  d) Asterix bails out at the failure in execution of a statement. As stated in (a), the failing statement is rolled back and has no impact on previously executed statements.
  e) Forward references during type creation are not supported. This is not a regression, as these did not work in the previous model either.
  f) Amongst the submitted statements, you could have multiple queries.

2) Asterix has support for AQL bodied functions. You can create AQL bodied fucntions and may use them in subsequent sessions. 

3) Asterix has support for cross dataverse statements. You can invoke statements/queries that refer to entities belonging to different dataverses. 

4) Other Issues resolved: 25, 62, 100, 124, 148, 165, 202  


git-svn-id: https://asterixdb.googlecode.com/svn/branches/asterix_stabilization@860 eaa15691-b419-025a-1212-ee371bd00084