Skip to content

Using native bindings causes difference in notification object #1045

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
makkeu opened this issue Jun 9, 2016 · 1 comment
Open

Using native bindings causes difference in notification object #1045

makkeu opened this issue Jun 9, 2016 · 1 comment
Labels

Comments

@makkeu
Copy link

makkeu commented Jun 9, 2016

When listening notifications, result message is different depending on what binding is used. With native bindings, message doesn't have name, length, or processId properties. Tested with version 4.5.1 and 5.0.0. pg-native version 1.10.0.

client.on('notification', function(msg) {
  // with js bindings msg contains name, length, processId, channel, payload
  // with native bindings msg only contains channel and payload
})
@sibedge
Copy link
Contributor

sibedge commented Jun 22, 2016

that's a known issue, at least the main part - parameter payload is there ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants