Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / jklingsporn/vertx-jooq issues and pull requests

#155 - Would it be possible to instantiate a DAO provided a transaction query execution

Issue - State: closed - Opened by wwelling over 4 years ago - 5 comments

#155 - Would it be possible to instantiate a DAO provided a transaction query execution

Issue - State: closed - Opened by wwelling over 4 years ago - 5 comments

#155 - Would it be possible to instantiate a DAO provided a transaction query execution

Issue - State: closed - Opened by wwelling over 4 years ago - 5 comments

#155 - Would it be possible to instantiate a DAO provided a transaction query execution

Issue - State: closed - Opened by wwelling over 4 years ago - 5 comments

#155 - Would it be possible to instantiate a DAO provided a transaction query execution

Issue - State: closed - Opened by wwelling over 4 years ago - 5 comments

#155 - Would it be possible to instantiate a DAO provided a transaction query execution

Issue - State: closed - Opened by wwelling over 4 years ago - 5 comments

#155 - Would it be possible to instantiate a DAO provided a transaction query execution

Issue - State: closed - Opened by wwelling over 4 years ago - 5 comments

#155 - Would it be possible to instantiate a DAO provided a transaction query execution

Issue - State: closed - Opened by wwelling over 4 years ago - 5 comments

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#153 - Support postgres bytea type in the reactive driver

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 2 comments
Labels: bug, reactive

#152 - Fix overly eager replacement of "." with nio.Path changes

Pull Request - State: closed - Opened by mykelalvis almost 5 years ago

#152 - Fix overly eager replacement of "." with nio.Path changes

Pull Request - State: closed - Opened by mykelalvis almost 5 years ago

#152 - Fix overly eager replacement of "." with nio.Path changes

Pull Request - State: closed - Opened by mykelalvis almost 5 years ago

#152 - Fix overly eager replacement of "." with nio.Path changes

Pull Request - State: closed - Opened by mykelalvis almost 5 years ago

#152 - Fix overly eager replacement of "." with nio.Path changes

Pull Request - State: closed - Opened by mykelalvis almost 5 years ago

#152 - Fix overly eager replacement of "." with nio.Path changes

Pull Request - State: closed - Opened by mykelalvis almost 5 years ago

#152 - Fix overly eager replacement of "." with nio.Path changes

Pull Request - State: closed - Opened by mykelalvis almost 5 years ago

#152 - Fix overly eager replacement of "." with nio.Path changes

Pull Request - State: closed - Opened by mykelalvis almost 5 years ago

#151 - Generation fails when module's path contains `.`

Issue - State: closed - Opened by mykelalvis almost 5 years ago - 1 comment
Labels: bug

#151 - Generation fails when module's path contains `.`

Issue - State: closed - Opened by mykelalvis almost 5 years ago - 1 comment
Labels: bug

#151 - Generation fails when module's path contains `.`

Issue - State: closed - Opened by mykelalvis almost 5 years ago - 1 comment
Labels: bug

#151 - Generation fails when module's path contains `.`

Issue - State: closed - Opened by mykelalvis almost 5 years ago - 1 comment
Labels: bug

#151 - Generation fails when module's path contains `.`

Issue - State: closed - Opened by mykelalvis almost 5 years ago - 1 comment
Labels: bug

#151 - Generation fails when module's path contains `.`

Issue - State: closed - Opened by mykelalvis almost 5 years ago - 1 comment
Labels: bug

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#150 - Getting ERROR Connection not open CLOSED when composing Futures using vertx-jooq-classic-reactive: 5.0.1

Issue - State: closed - Opened by nixos89 almost 5 years ago - 15 comments
Labels: feedback required

#149 - dao.insertReturningPrimary fails with java.util.NoSuchElementException

Issue - State: closed - Opened by marioc-bitheads almost 5 years ago - 5 comments
Labels: bug

#149 - dao.insertReturningPrimary fails with java.util.NoSuchElementException

Issue - State: closed - Opened by marioc-bitheads almost 5 years ago - 5 comments
Labels: bug

#149 - dao.insertReturningPrimary fails with java.util.NoSuchElementException

Issue - State: closed - Opened by marioc-bitheads almost 5 years ago - 5 comments
Labels: bug

#149 - dao.insertReturningPrimary fails with java.util.NoSuchElementException

Issue - State: closed - Opened by marioc-bitheads almost 5 years ago - 5 comments
Labels: bug

#149 - dao.insertReturningPrimary fails with java.util.NoSuchElementException

Issue - State: closed - Opened by marioc-bitheads almost 5 years ago - 5 comments
Labels: bug

#149 - dao.insertReturningPrimary fails with java.util.NoSuchElementException

Issue - State: closed - Opened by marioc-bitheads almost 5 years ago - 5 comments
Labels: bug

#149 - dao.insertReturningPrimary fails with java.util.NoSuchElementException

Issue - State: closed - Opened by marioc-bitheads almost 5 years ago - 5 comments
Labels: bug

#148 - JSONB to JsonObject Convertor Failure when using postgres reactive classic

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 3 comments
Labels: bug

#148 - JSONB to JsonObject Convertor Failure when using postgres reactive classic

Issue - State: closed - Opened by gtejasvi almost 5 years ago - 3 comments
Labels: bug

#147 - Limit in classic JDBC DAO?

Issue - State: closed - Opened by activey almost 5 years ago - 1 comment
Labels: enhancement

#147 - Limit in classic JDBC DAO?

Issue - State: closed - Opened by activey almost 5 years ago - 1 comment
Labels: enhancement

#147 - Limit in classic JDBC DAO?

Issue - State: closed - Opened by activey almost 5 years ago - 1 comment
Labels: enhancement

#147 - Limit in classic JDBC DAO?

Issue - State: closed - Opened by activey almost 5 years ago - 1 comment
Labels: enhancement

#147 - Limit in classic JDBC DAO?

Issue - State: closed - Opened by activey almost 5 years ago - 1 comment
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#146 - Default conversion of java.util.time types

Issue - State: closed - Opened by jklingsporn almost 5 years ago
Labels: enhancement

#145 - AbstractVertxDAO.update() ignores optimistic locking

Issue - State: open - Opened by badgerwithagun almost 5 years ago - 6 comments
Labels: bug, enhancement

#145 - AbstractVertxDAO.update() ignores optimistic locking

Issue - State: open - Opened by badgerwithagun almost 5 years ago - 6 comments
Labels: bug, enhancement

#145 - AbstractVertxDAO.update() ignores optimistic locking

Issue - State: open - Opened by badgerwithagun almost 5 years ago - 6 comments
Labels: bug, enhancement

#145 - AbstractVertxDAO.update() ignores optimistic locking

Issue - State: open - Opened by badgerwithagun almost 5 years ago - 6 comments
Labels: bug, enhancement

#145 - AbstractVertxDAO.update() ignores optimistic locking

Issue - State: open - Opened by badgerwithagun almost 5 years ago - 6 comments
Labels: bug, enhancement

#145 - AbstractVertxDAO.update() ignores optimistic locking

Issue - State: open - Opened by badgerwithagun almost 5 years ago - 6 comments
Labels: bug, enhancement

#145 - AbstractVertxDAO.update() ignores optimistic locking

Issue - State: open - Opened by badgerwithagun almost 5 years ago - 6 comments
Labels: bug, enhancement

#145 - AbstractVertxDAO.update() ignores optimistic locking

Issue - State: open - Opened by badgerwithagun almost 5 years ago - 6 comments
Labels: bug, enhancement

#143 - Fix enum handling if enum is not defined in database

Issue - State: closed - Opened by jklingsporn almost 5 years ago

#143 - Fix enum handling if enum is not defined in database

Issue - State: closed - Opened by jklingsporn almost 5 years ago

#143 - Fix enum handling if enum is not defined in database

Issue - State: closed - Opened by jklingsporn almost 5 years ago

#143 - Fix enum handling if enum is not defined in database

Issue - State: closed - Opened by jklingsporn almost 5 years ago

#143 - Fix enum handling if enum is not defined in database

Issue - State: closed - Opened by jklingsporn almost 5 years ago

#143 - Fix enum handling if enum is not defined in database

Issue - State: closed - Opened by jklingsporn almost 5 years ago