Skip to content
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

Interpretation of NextToken? #15

Open
gravelld opened this issue Jul 15, 2014 · 3 comments
Open

Interpretation of NextToken? #15

gravelld opened this issue Jul 15, 2014 · 3 comments

Comments

@gravelld
Copy link

Just wondering if SdbNavigator interprets NextToken correctly?

I ask because if I run:

select count(*) from `My-Domain`

I get different results each time I run. The domain has about 5m items in, so in a normal SDB select query this would return NextToken as it tots up the result.

@Reggino
Copy link
Owner

Reggino commented Jul 15, 2014

Yes, i think it does ;-) You may open the "Developer Tools > Network" in chrome and see the actual call being made and how the NextToken is processed and passed between requests.

@Reggino
Copy link
Owner

Reggino commented Jul 15, 2014

To be more precise: It should work, however i do not have a data-set a big as yours to confirm this.

By looking at the query via the developer tools you may confirm that the actual query performed should be correct.

If you experience any issues, please let me know.

@gravelld
Copy link
Author

Yes, I think I can see the calls being made correctly. However the end result is incorrect. Given n calls using NextToken, it gives only the final result in the nth call. In this case, around '300000'.

Now, when you use the CLI you have to then sum all the results together, because this is a count(*) call.

Maybe the UI doesn't have the logic to sum all the results? It is logic specific to count(*).

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

No branches or pull requests

2 participants