-
### What is the problem this feature would solve?
Support very popular data type `Decimal` ([decimal.js](https://github.com/MikeMcl/decimal.js)). Currently there is no way to do anything with it, sin…
-
Reading from a stored procedure a field DECIMAL(38,20) returns some wrong numbers due to wrong parsing of the value.
EX: Number 1000 will be returned as 999.9999999999999....
Using the library D…
-
## Description
Currently in various places we pass amounts from UI to the backend as a JS number.
In most cases it works seamlessly but there are corner cases we should take into account to provid…
-
### Describe the enhancement requested
cc @domoritz
Current JS documentation is not clear on how to read & manipulate the data from Apache Arrow JS
JS version of Apache Arrow is used in JS env…
-
The rounding issues that essentially led to creating the DECIMAL cql type would dictate such columns to be returned as strings, to let callers/users/clients to do the right thing. Otherwise, unexpecte…
-
I'm using the [next-superjson-plugin](https://github.com/blitz-js/next-superjson-plugin) to pass data from next.js server components to client components and this works like a charm.
Besides server…
-
@erights [commented](https://github.com/tc39/proposal-decimal/issues/51#issuecomment-587514013) that, if there's a built-in decimal type in JavaScript, Agoric wouldn't use it. I'd like to learn more a…
-
Je crée un nouveau noeud dans le graphe :
```
...
var sensor0 = graph.newNode(0, 0);
sensor0.set("name", "sensor0");
sensor0.set("value", 30.0);
...
```
Puis quand je récupère l'attribut en …
-
When you run a query on BigInt column, I would expect it to return the result in JS native BigInt type instead of regular int which is 4 bytes and therefore truncates the result
-
Hi @bakkot, thanks for this proposal!
When I was reading [the `Math.sumPrecise` proposal tweet](https://twitter.com/robpalmer2/status/1777772402472046684) from @robpalme, I somehow read into it tha…