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

DataError in Microsoft Edge #95

Open
bennycode opened this issue Feb 5, 2016 · 5 comments
Open

DataError in Microsoft Edge #95

bennycode opened this issue Feb 5, 2016 · 5 comments

Comments

@bennycode
Copy link

Hello, by using YDN in my web application with Microsoft Edge I am getting a DataError. The JavaScript inspector says it comes from key_range.js (265,3).

I am using:

When I run the same code in Chrome or Firefox, then it works.

@yathit
Copy link
Owner

yathit commented Feb 5, 2016

Yes, it is known issue for over three years now. MS don't have time to fix, so I am.

@bennycode
Copy link
Author

So can you tell me what's the problem in Edge? Why is it complaining? Maybe I can setup a different database schema to go work around this issue.

@yathit
Copy link
Owner

yathit commented Feb 5, 2016

Yes, avoid multiEntry and compound index. See more on https://dev.yathit.com/ydn-db/doc/setup/limitation.html

@bennycode
Copy link
Author

Ok, thanks for the fast reply. So with Edge I cannot use a schema like this:

{
  name: 'name, timestamp',
  keyPath: [
    'name', 'timestamp'
  ]
}

But this is needed when I want to do queries like:

db.from('users').where('name', '=', 'Homer').order('timestamp');

Is there another way of not using a compound index but being able to query by name and order by timestamp?

@mtycholaz
Copy link

There is support in Edge for basic IndexDb. They're considering adding more complex features. More info from Microsoft regarding this here.

https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/8437039-full-feature-support-for-indexeddb

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

No branches or pull requests

3 participants