question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Expression error when using a having('key').between(1, 10)

See original GitHub issue

I using the library and working good. In this point I found this error. I resolved this error using the native aws-sdk and works well.

##Error

{
  "message": "Value provided in ExpressionAttributeValues unused in expressions: keys: {:create_at_2_v1, :create_at_1_v1}",
  "code": "ValidationException",
  "time": "2016-11-23T18:06:22.315Z",
  "requestId": "CVAO4IP0SKPNVCULVHTTS7DC8RVV4KQNSO5AEMVJF66Q9ASUAAJG",
  "statusCode": 400,
  "retryable": false,
  "retryDelay": 0
}

##Example

//...
    function (init, end) {
        const def = new Defer();
        const initDate = new Date(init);
        const endDate = new Date(end);

        console.log(+initDate, +endDate); // log for test
        
        dynamodb
          .table('table')
          .having('key1').null()
          .having('create_at').between(+initDate, +endDate)
          .scan(function(err, data) {
              if (err) return def.reject(err);
              def.resolve(data);
          });

        return def.promise;
    }
//...

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:10 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
adrianprajacommented, Nov 23, 2016

I see the problem, I’ll try to reproduce

0reactions
adrianprajacommented, Nov 25, 2016

released version 0.1.60,

with minimum changes this fixed my local replication of your described issue.

I still can not recommend using

	var $users = DynamoDB.table('users')
	$users.insert(...)
	$users.update(...)
	...

there are no tests to confirm that is ready for this change.

I’m closing the issue for now, please re-open it if you still see the issue.

Thanks </adrian>

Read more comments on GitHub >

github_iconTop Results From Across the Web

Expression Error.: The key didn't match any rows in the table
For me this error was caused by bad login credentials. I cannot get past this error. It is when trying to update a...
Read more >
Expression.Error: The key did not match any rows in the table
Solved: I have a data set that has refreshed successfully in the past. It was built 3 days ago and refreshed fine for...
Read more >
Understanding The “The key didn't match any rows in the table ...
One of the most common errors you'll see when working with Power Query in Power BI or Excel is this: Expression.Error: The key...
Read more >
SQLSTATE values and common error codes - IBM
SQLSTATE values are comprised of a two-character class code value, ... 10, XQuery Error, Table 12 ... 01540, A limit key has been...
Read more >
Scheme - Expressions
Primitive expression types include variables and procedure calls. ... it is an error to alter a constant (i.e. the value of a literal...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found