Comments (7)
This falls out of my scope, but being aware of how many times I have tagged - assigning to myself. Going to bring up in next eng meet about how we spread and prioritise workload.
For the ticket: It would seem that there is processing on the document, but I don't understand how that would happen since deletes don't really process the document. @DelSkayn if you have any input that would be appreciated!
from surrealdb.
I am looking into this but I am currently getting a different error. I downloaded the surreal deal dataset and imported it successfully. I am however facing an issue the order relation. All orders are related via a order record id which consists of a country and seemingly a datetime. However the datetime is in the form of 2023-01-04T03:55:50.718612
. This is an invalid datetime as it is missing a timezone. So the current error I am getting is that 2023-01-04T03:55:50.718612
can't be converted to a datetime.
from surrealdb.
Ive noticed errors during deletes because of futures/events that are getting fired that are now invalid based on the calculation of the deleted data.
Mine was a event that accessed $after.field, and that field was a future that became "broken" from the DELETE
, so it was a underlying query not the actual DELETE
that was erroring.
Is this related to those records that cause issues? (not got access to surreal to test currently)
from surrealdb.
So the current error I am getting is that
2023-01-04T03:55:50.718612
can't be converted to a datetime.
Interesting, once I upgraded to v1.1 I also get that error 🤔
from surrealdb.
The datetime error seems to be a different error: Previously there was some dubious behavior when parsing date-times. If only a part of the string matched a datetime it would still parse the datetime. so 2012-04-23blablabla
would parse the 2012-04-23
part and ignore the blablabla. So with 2012-04-23T18:25:43.5110000
it fails to parse the full datetime since the time zone is missing and therefore would only parse 2012-04-23
. Now it errors instead if there is still some text left which causes the error I found.
Updating the dataset to have the correct datetimes makes the multiplication error return.
from surrealdb.
I believe this issue can be closed. The problem seemed to be inside one of the queries where it would try to multiply a number times a null because of a missing else branch so the error message was actually correct.
We still have a problem that the error message here is not that useful but that should probably be a different issue.
from surrealdb.
For those interested what the actual problem was, in the sureal-deal dataset there was the query:
DEFINE TABLE daily_sales SCHEMALESS AS
SELECT count() AS number_of_orders,
time::format(<datetime> order_date, '%Y-%m-%d') AS day,
math::sum((price * IF discount = NONE THEN 1 END) * quantity) AS sum_sales,
currency FROM order GROUP BY day, currency;
Which should have been:
DEFINE TABLE daily_sales SCHEMALESS AS
SELECT count() AS number_of_orders,
time::format(<datetime> order_date, '%Y-%m-%d') AS day,
math::sum((price * IF discount = NONE THEN 1 ELSE discount END) * quantity) AS sum_sales,
currency FROM order GROUP BY day, currency;
from surrealdb.
Related Issues (20)
- Feature: Query builder like syntax
- Bug: Paginating data (START / OFFSET) gets exponential slower with bigger datasets (from 380ms to 468970ms) HOT 1
- Bug: Cannot insert/create a data that contains a large vector size HOT 8
- Feature: Automatically create/update records of child based on definition in parent or id in child
- Parameters do not work in string functions HOT 5
- Feature: Omit in fetch
- Feature: Live Query WHERE clause should process Params HOT 4
- Bug: Delr is displayed in trace logs of releases HOT 1
- Bug: I upgraded my server surreal version and lost all my data HOT 8
- Bug: OPTION IMPORT causes bugs with FTS indexes
- Bug: subquery runs create twice
- Feature: Embedded replicas
- Bug: TIMEOUT not respected inside RETURN statement
- Bug: Rust fails to build surrealdb HOT 10
- Bug: Parser interpretes string id with starting with number followed by 'e' as exponenets HOT 2
- Bug: COMPOSITE INDEX does not work
- Bug: 'Unsupported value' in no-index WHERE condition, causes INDEX to not be used HOT 1
- Bug: The alphabetical order of the properties of an object-based Record ID is query-significant
- Bug: HTTP CREATE not working when using TOKEN auth HOT 2
- Bug: Can't define a schema with flexible object keys
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from surrealdb.