{"json_modified": "2016-05-05T03:22:59.682572", "uuid": "2ece8391-bdc3-4417-b887-8ba34bc08c20", "title": "IDBRequest.transaction", "url": "/en-US/docs/Web/API/IDBRequest/transaction", "tags": ["API", "storage", "IndexedDB", "Reference", "Property", "Database", "IDBRequest", "indexeddb", "Storage", "transaction"], "translations": [{"uuid": "e0e4bd27-3103-421e-b172-e6a328b407b8", "title": "IDBRequest.transaction", "url": "/fr/docs/Web/API/IDBRequest/transaction", "tags": [], "summary": "La propri\u00e9t\u00e9 <strong><code>transaction</code></strong> de l'interface IDBRequest renvoie la <a href=\"/fr/docs/Web/API/IDBTransaction\" title=\"L'interface IDBTransaction de l' API IndexedDB permet en utilisant ses attributs &#xE9;v&#xE9;nementiels, d'effectuer des transactions statiques asynchrones sur une base de donn&#xE9;es . Toute lecture et &#xE9;criture de donn&#xE9;es se font par des transactions. On utilise en fait IDBDatabase pour d&#xE9;marrer une transaction et IDBTransaction pour en r&#xE9;gler le mode (ex: readonly ou readwrite ), et acc&#xE9;der &#xE0; un IDBObjectStore pour faire une requ&#xEA;te. On peut &#xE9;galement l'utiliser pour annuler les transactions.\"><code>transaction</code></a> dans laquelle on fait la requ\u00eate.La propri\u00e8t\u00e8 peut renvoiyer <code>null</code> si requ\u00eate se fait sans transaction, comme un objet IDBRequest renvoy\u00e9 par <a href=\"/fr/docs/Web/API/IDBFactory/open\" title=\"La m&#xE9;thode open() de l'interface IDBFactory demande l'ouverture d'une connection &#xE0; une base de donn&#xE9;es.\"><code>IDBFactory.open</code></a> dans ce cas on est juste connect\u00e9 \u00e0 la base de donn\u00e9es.", "localization_tags": [], "locale": "fr", "last_edit": "2016-05-05T03:22:55", "review_tags": ["technical", "editorial"]}], "modified": "2016-05-02T23:14:39", "label": "IDBRequest.transaction", "localization_tags": [], "locale": "en-US", "id": 84407, "last_edit": "2016-03-22T10:58:26", "summary": "An <a href=\"/en-US/docs/Web/API/IDBTransaction\" title=\"Note that as of Firefox 40, IndexedDB transactions have relaxed durability guarantees to increase performance (see bug&#xA0;1112702.) Previously in a readwrite transaction IDBTransaction.oncomplete was fired only when all data was guaranteed to have been flushed to disk. In Firefox 40+ the complete event is fired after the OS has been told to write the data but potentially before that data has actually been flushed to disk. The complete event may thus be delivered quicker than before, however, there exists a small chance that the entire transaction will be lost if the OS crashes or there is a loss of system power before the data is flushed to disk. Since such catastrophic events are rare most consumers should not need to concern themselves further.\"><code>IDBTransaction</code></a>.", "sections": [{"id": "Quick_Links", "title": null}, {"id": "Syntax", "title": "Syntax"}, {"id": "Value", "title": "Value"}, {"id": "Example", "title": "Example"}, {"id": "Specifications", "title": "Specifications"}, {"id": "Browser_compatibility", "title": "Browser compatibility"}, {"id": "See_also", "title": "See also"}], "slug": "Web/API/IDBRequest/transaction", "review_tags": []}