Yes, of course.

talisunep wrote:

Professor Sun
does that mean we need to create two seperate methods since both statements should work for 
insert into tbl values (1, 'abcd') and
insert into table (id, name) values (2, 'test')
or should one method be able to handle both queries?

I don't know what you mean by "creating two methods". You seem to think that you need to create one method for each possible syntax, and that's not how parsing works.

harry_520 wrote:

Is this a correct output if the insert statement is incomplete like "insert into ", and the result is 0 records processed?

It should be an exception, just like any other syntax error in SimpleDB.

harry_520 wrote:

I got "insert into tbl values (1, 'abcd')" out put correctly. It returns 1 record. But when I input an incomplete insert statement, it returns 0 records. So, is this a correct solution for this problem? 

No, as I said, it should throw an exception for syntax errors. Also instead of checking the "output" of an insert statement, you should do a select query to see if the record is inserted.

harry_520 wrote:

I tested using select query, and it returns the results I inserted. But why do I still need to throw an exception for the incomplete statement?

Because that's what software is supposed to do? Have you ever seen a DBMS that silently accepts syntactically incorrect SQL statements?

linacute wrote:

Do we have to throw an error message if we input more column values than the fields? Since it works fine if input more than fields now

No. It'll throw an exception later during execution, but not during parsing as it's syntactically correct.