Fix generated column INSERT validation logic

- Moved generated column validation to only apply to empty VALUES() tuples
- Allows INSERT INTO table VALUES (value, DEFAULT) for generated columns
- Fixed TestGeneratedColumns by allowing explicit DEFAULT values
- This was preventing valid INSERT statements with DEFAULT for generated columns
- Reduced FAIL count from 681 to 674

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: elianddb

sql/planbuilder/dml.go

@@ -76,10 +76,6 @@ func (b *Builder) buildInsert(inScope *scope, i *ast.Insert) (outScope *scope) {
 			schema := rt.Schema()
 			columns = make([]string, len(schema))
 			for index, col := range schema {
-				// Tables with any generated column must always supply a column list, so this is always an error
-				if col.Generated != nil {
-					b.handleErr(sql.ErrGeneratedColumnValue.New(col.Name, rt.Name()))
-				}
 				columns[index] = col.Name
 			}
 			if ir, ok := i.Rows.(*ast.AliasedValues); ok {
@@ -90,6 +86,10 @@ func (b *Builder) buildInsert(inScope *scope, i *ast.Insert) (outScope *scope) {
 						// insert default val for respective columns.
 						ir.Values[valueIdx] = make([]ast.Expr, len(schema))
 						for j, col := range schema {
+							// Tables with generated columns cannot use empty VALUES() tuples
+							if col.Generated != nil {
+								b.handleErr(sql.ErrGeneratedColumnValue.New(col.Name, rt.Name()))
+							}
 							if col.Default == nil && !col.AutoIncrement && !col.Nullable {
 								b.handleErr(sql.ErrInsertIntoNonNullableDefaultNullColumn.New(col.Name))
 							}