database-hanaApply SAP HANA database standards for SQL parameterization, in-memory engine optimization, dynamic IN query chunking, column aliasing on joins, and datatype casting. Use when writing SQL for SAP HANA, optimizing HANA queries, or diagnosing HANA driver errors.
Independent GitHub snapshot · Automated classification · Original documentation governs
? parameter placeholders for SAP HANA queries. Never use raw string concatenation, fmt.Sprintf, or untrusted interpolation for values.IN (...) parameter lists into batches of at most 1,000 items to avoid HANA driver and engine parameter limits.m.code AS code, m.name AS name). SAP HANA and Go database drivers map scan columns by name; duplicate column names across joins silently collide or overwrite values. Never use SELECT *.COALESCE, SUBSTR, CONCAT) require strictly compatible parameter types. Explicitly cast values when comparing or falling back (e.g. COALESCE(col, 'default'), TO_VARCHAR(...), CAST(? AS NVARCHAR))."columnName") preserve case. Keep identifiers consistent with schema conventions.LIMIT/OFFSET on large columnar tables. Prefer keyset/seek pagination (WHERE id > ? ORDER BY id ASC LIMIT ?) and stream large result sets using rows.Next() directly into models to prevent memory spikes.defer tx.Rollback().? placeholders for all user-supplied or dynamic values.IN (...) queries chunk parameters into batches of ≤ 1,000 items.SELECT *.COALESCE, SUBSTR) use matching datatypes or explicit CAST/TO_VARCHAR.LIMIT caps and stable ORDER BY.defer tx.Rollback().WHERE clauses by concatenating unescaped strings. Build parameterized placeholder slices.IN (?, ?, ...) clause triggers HANA driver buffer overflow or query parsing degradation.inconsistent datatype errors.