michaelwittig/node-q

Issues

• Incorrect timestamp values inserted

  #71 opened a year ago by victor-ono
  0

• Cannot use TLS when using Typescript as the typings file is not accurate

  #69 opened a year ago by caleteeter
  1

• How can I connect with TLS, but without verification?

  #63 opened 3 years ago by travis-leith
  1

• 同学，您这个项目引入了99个开源组件，存在20个漏洞，辛苦升级一下

  #62 opened 3 years ago
  0

• Infinty for different data types

  #55 opened 4 years ago by jerry40
  4

• BigInt for long

  #48 opened 5 years ago by emilbayes
  1

• make upd function configurable

  #38 opened 7 years ago by markmcdowell
  1

• Typed - functional select

  #36 opened 7 years ago by richardbutler
  3

• problem with the net module when used inside react app

  #59 opened 3 years ago by bitcorr
  1

• Type Definition Errors

  #54 opened 4 years ago by ChrisCates
  1

• Logging Q query output

  #53 opened 4 years ago by nabils
  1

• backtick escape issue for symbol

  #51 opened 4 years ago by cheduo
  3

• Dates reduced by a few nanoseconds when sent to KDB

  #45 opened 6 years ago by wwarby
  9

• Serialiser does not escape the null character in strings, causing badmsg error

  #43 opened 6 years ago by wwarby
  1

• Errors not returned when using conn.ks

  #42 opened 6 years ago by wwarby
  2

• Calling upd with tablular data

  #41 opened 6 years ago by wwarby
  2

• Precision error on real (explicit) type:

  #40 opened 6 years ago by jacobloveless
  3

• Error at .deserialize when inserting to table

  #39 opened 6 years ago by kysely
  6

• Localtime is assumed to be UTC..

  #37 opened 7 years ago by deepgnly
  11

• Unicode string turns into a messy code

  #35 opened 7 years ago by liutongwei
  5

• doesn't support unicode and calls with unicode strings cause stream to hang

  #17 opened 9 years ago by thekvn
  11

• Custom upd

  #31 opened 7 years ago by amirburbea
  3

• Deserialization for remote compressed ipc calls sometimes fails

  #30 opened 8 years ago by thekvn
  3

• passing an array or object where the only values are null fails serialization causes connection to lock up

  #29 opened 8 years ago by thekvn
  1

• null for time type

  #26 opened 8 years ago by ritalg
  2

• Error condition being triggered unexpectedly

  #12 opened 8 years ago by richardbutler
  11

• Server crash when using node v0.10.31

  #24 opened 8 years ago by tsuk13
  1

• timezone

  #25 opened 8 years ago by ritalg
  1

• Problem when using 'strict mode'

  #20 opened 9 years ago by komsit37
  3

• Queries with 'by' clauses do not return results

  #18 opened 9 years ago by savvione
  2

• Space decoded to "null"

  #15 opened 9 years ago by iuhh
  1

• charCode 32 (" ") deserialized into null

  #13 opened 9 years ago by thekvn
  3

• issue parsing negative number

  #9 opened 9 years ago by komsit37
  3

• Command getting corrupted through serialisation?

  #8 opened 9 years ago by richardbutler
  5

• Not compatible with nodejs 0.12

  #7 opened 10 years ago by michaelwittig
  1

• handle chunk data packages

  #1 opened 10 years ago by michaelwittig
  0

• Only recognize sync replies for request/response answeres

  #2 opened 10 years ago by michaelwittig
  0