Skip to content
Snippets Groups Projects
Select Git revision
  • ee1461eeed2a150ae1e70390e8e98ee79aacd126
  • master default protected
  • devel
  • hruska-feature-clients-api
  • malostik-#5066-deduplicate-idea-ids
  • warden-postgresql-port
  • hruska-feature-#6799-filter-keys
  • hruska-feature-5066-duplicateIdeaID
  • warden-client-3.0-beta3
  • warden-server-3.0-beta3
  • warden-client-2.2-final
  • warden-server-2.2-final
  • warden-client-3.0-beta2
  • warden-server-3.0-beta2
  • warden-client-2.2
  • warden-server-2.2-patch3
  • warden-client-3.0-beta1
  • warden-server-3.0-beta1
  • warden-server-2.2-patch1
  • warden-client-3.0-beta0
  • warden-server-3.0-beta0
  • warden-server-2.2
  • warden-server-2.1-patch1
  • warden-client-2.1
  • warden-server-2.1
  • warden-server-2.1-beta6
  • warden-server-2.1-beta5
  • warden-server-2.1-beta4
28 results

warden

  • Clone with SSH
  • Clone with HTTPS
  • Forked from 713 / Warden / Warden - archive
    Source project has a limited visibility.
    user avatar
    ph authored
    On MySQLdb (1.2.2) we still experience stale uncommitted transactions and different warden_server processes don't see actual db data. Looks like there is at least one stale transaction per daemon, appearing at any call to execute. I have no better idea than to implicitly commit after each SELECT (INSERTs are committed/rolled back explicitly).
    ee1461ee
    History
    Name Last commit Last update