Skip to content

Make a version of sql.js compiled with ALLOW_MEMORY_GROWTH=1 #143

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

Merged
merged 3 commits into from
Mar 18, 2016

Conversation

dinedal
Copy link
Collaborator

@dinedal dinedal commented Mar 11, 2016

Make a version of sql.js compiled with ALLOW_MEMORY_GROWTH=1 available for everyone, keep it up to date as part of releases

Closes #113

dinedal and others added 2 commits March 10, 2016 18:53
… for everyone, keep it up to date as part of releases

Closes sql-js#113
* master:
  Adds `db.getRowsModified` with docs.
@dinedal
Copy link
Collaborator Author

dinedal commented Mar 11, 2016

@lovasoa this is ready for merge as well, would appreciate your thoughts here

@lovasoa
Copy link
Member

lovasoa commented Mar 11, 2016

Looks ok! Maybe you should mention the existence of this file in the README, so that people knew about it.

At the end of the README, there is a downloads section. You could update it and mention your new memory growth version. And while you're at it, you could also mention sql-debug.js there.

@dinedal
Copy link
Collaborator Author

dinedal commented Mar 18, 2016

@lovasoa any update here?

lovasoa added a commit that referenced this pull request Mar 18, 2016
Make a version of sql.js compiled with ALLOW_MEMORY_GROWTH=1
@lovasoa lovasoa merged commit 05b28e5 into sql-js:master Mar 18, 2016
@lovasoa
Copy link
Member

lovasoa commented Mar 18, 2016

Oh, sorry, I didn't see your last commit !

@lovasoa
Copy link
Member

lovasoa commented Mar 18, 2016

I just merged. Again, sorry for the delay, I thought you hadn't updated the README.

@dinedal
Copy link
Collaborator Author

dinedal commented Mar 18, 2016

No worries! Thanks for the merge!

@danacalcaianu
Copy link

I had the same problem with the memory errors and switched to this version but I'm wondering what are the main differences between the two and what important issues this might rise?

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

Successfully merging this pull request may close these issues.

3 participants