René's URL Explorer Experiment

{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://sqlint.com/#organization","name":"SqlInt","url":"https://sqlint.com","logo":"https://sqlint.com/og-image.jpg","email":"support.sqlint@gmail.com","description":"SqlInt is a browser-based SQL practice and interview-preparation platform that also provides free client-side SQL tools for developers.","disambiguatingDescription":"SqlInt (sqlint.com) is a browser-based SQL practice and interview-preparation website with free client-side SQL tools - a web platform, not a command-line utility.","contactPoint":{"@type":"ContactPoint","contactType":"customer support","email":"support.sqlint@gmail.com","availableLanguage":["en"]},"subjectOf":[{"@type":"WebPage","url":"https://sqlint.com/about","name":"About SqlInt"}],"sameAs":[]},{"@type":"WebSite","@id":"https://sqlint.com/#website","url":"https://sqlint.com","name":"SqlInt","description":"SqlInt is a browser-based SQL practice and interview-preparation platform that also provides free client-side SQL tools for developers.","publisher":{"@id":"https://sqlint.com/#organization"}}]}

{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://sqlint.com"},{"@type":"ListItem","position":2,"name":"Learn SQL","item":"https://sqlint.com/learn-sql"},{"@type":"ListItem","position":3,"name":"Transactions & COMMIT / ROLLBACK","item":"https://sqlint.com/learn-sql/transactions-commit-rollback"}]}

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Why are long-running transactions a problem?","acceptedAnswer":{"@type":"Answer","text":"They hold locks on the rows they touched, blocking other writers, and force the engine to keep old row versions alive for their snapshot (bloat in PostgreSQL's vacuum, long undo logs in MySQL/InnoDB). Keep transactions short: do the reading and computing in the app, then transact only the writes."}},{"@type":"Question","name":"If every statement auto-commits, why do I ever see 'idle in transaction'?","acceptedAnswer":{"@type":"Answer","text":"Because a transaction was opened (BEGIN, or a failed statement in some drivers) and never finished — usually a connection that errored out mid-flow. Those sessions hold locks and bloat forever until killed. Always pair BEGIN with COMMIT/ROLLBACK, including on error paths."}}]}

{"@context":"https://schema.org","@type":"LearningResource","@id":"https://sqlint.com/learn-sql/transactions-commit-rollback#learning-resource","name":"Transactions & COMMIT / ROLLBACK — SQL Tutorial with Examples","description":"Learn SQL Transactions & COMMIT / ROLLBACK. Includes syntax, examples, mistakes, and interview tips.","speakable":{"@type":"SpeakableSpecification","cssSelector":["h1",".topic-explanation"]},"citation":["https://www.postgresql.org/docs/current/sql.html","https://sqlite.org/lang.html","https://www.postgresql.org/docs/current/tutorial.html"],"isPartOf":{"@id":"https://sqlint.com/learn-sql#course"},"educationalLevel":"Advanced","teaches":["Syntax: BEGIN TRANSACTION;\n-- SQL statements\nCOMMIT;\n-- or\nROLLBACK;\n\nSAVEPOINT sp_name;\nROLLBACK TO sp_name","Core concept: A transaction is a unit of work that either completes fully or not at all. Use BEGIN/START TRANSACTI","Common mistakes: Forgetting to COMMIT — changes sit in an open transaction and lock rows, blocking other queries. Lon","Interview tips: Explain isolation levels: READ UNCOMMITTED (dirty reads), READ COMMITTED (default in most DBs), REPE"],"timeRequired":"12 mins","about":{"@type":"Thing","name":"SQL","description":"Structured Query Language"},"audience":{"@type":"EducationalAudience","educationalRole":"student"},"author":{"@type":"Organization","@id":"https://sqlint.com/#organization","name":"SqlInt"},"url":"https://sqlint.com/learn-sql/transactions-commit-rollback"}