query always returns empty array
See original GitHub issueconst users = await client.query(`SELECT * FROM users`)
expected behavior returns array of objects with data from database.
actual behavior returns an empty array.
server info innodb_version: 5.6.45-86.1 protocol_version: 10 version: 10.1.43-MariaDB
The test database has actual data stored, works with other clients. I logged some received data in connection.ts. Looks like the field names are received but not the values.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Sanity query always return empty array - Stack Overflow
I have found the solution. I needed to switch the project from private to public. It's a blog by the way. enter image...
Read more >query always returns empty array · Issue #29 - GitHub
I make a very simple query. I send to three different databases. Two of them work as expected. The third will return an...
Read more >mongoDB autocomplete returns empty array - Atlas Search
The search always returns an empty array. I am using Atlas on the free tier. I have set up a Search Index as...
Read more >[Solved]-Mongoose query returns empty array-mongodb
Related Query · Mongoose find query on nested objects returns empty array · Mongoose query returns empty array · Mongoose query always returns...
Read more >$wpdb->get_results(...) with $wpdb->prepare(...) returns empty ...
$query = "SELECT * FROM {$wpdb->prefix}postmeta WHERE meta_key=%s AND ... $prepared_query = $wpdb->prepare($query, array($key,$value)); ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yeah I did. Getting following console output (like the other issue I posted):
Closing this because of inactivity. Not sure, I don’t know if the bug is fixed. Else feel free to reopen.