sql
MySQL binary logging unsafe statement
Binary logging not possible.*binlog_format.*STATEMENT.*unsafe
Fixes
- 1.Switch to ROW-based replication: SET GLOBAL binlog_format = 'ROW'
- 2.Avoid non-deterministic functions (UUID(), NOW(), RAND()) in statements with STATEMENT format
- 3.Use MIXED format as compromise: SET GLOBAL binlog_format = 'MIXED'
mysqlreplicationbinlog
Related Errors
sql3 fixes
PostgreSQL JSONB extracting from scalar
ERROR:.*cannot extract elements from a scalar.*jsonb
- •Check value is an object/array before extraction: jsonb_typeof(col) = 'object'
- •Use COALESCE with '{}' for null/scalar values
sql3 fixes
PostgreSQL JSONB operator type mismatch
ERROR:.*operator does not exist.*jsonb @> text
- •Cast the right operand to jsonb: col @> '{"key": "val"}'::jsonb
- •Use ->> operator for text extraction instead of ->
sql3 fixes
PostgreSQL full-text search config not found
ERROR:.*text search configuration.*does not exist
- •Create the text search configuration or use a built-in one (english, simple)
- •Install the pg_catalog extension if using a custom configuration