I also have the caveat that I would never use a proprietary database.

If you could show that it was faster or more portable than sql-lite, maybe 
because you didn't have to make the hop to C, then maybe it would be useful.  
But I don't see why this would be an improvement over just using SQLite 
bindings, if you had the kind of problem SQLite solves. 

If you wanted to run the same code on the server as on the client, not having 
to change your interface would be useful.  But most cases where you're running 
code in a browser and also want to run it on the server, you don't want to be 
using SQLite on the server.  A better solution would be to allow users to write 
their own persistence layer, and provide adapters for all the mainstream db's.
 
Ted

On Oct 9, 2012, at 4:27 PM, Daniel Rinehart <[email protected]> wrote:

> The lack of licensing or cost information on the website leads me to
> not even think about uses for the product.
> 
> -- Daniel R. <[email protected]> [http://danielr.neophi.com/]
> 
> 
> On Tue, Oct 9, 2012 at 4:58 PM, John Fowler <[email protected]> wrote:
>> Hello Node.js gurus,
>> 
>> I'm relatively new to Node.js, so please forgive the simplicity of this
>> question:  Would there be a use for a JavaScript Relational Database Engine
>> like SequelSphere?
>> 
>> SequelSphere is a new product to the HTML5 market that touts being it's own
>> relational database engine including a SQL parser and execution engine.  It
>> is currently targeted at the client side of architecture to provide a
>> mechanism for storing relational data (since the WebSQL standard was
>> abandoned).  Since it has it's own SQL engine, it truly works cross-browser,
>> and it persists its data via localStorage and indexedDB.
>> 
>> However, I'm assuming that since Node.js runs on the server, that it would
>> have a whole host of much more mature relational database technologies to
>> choose from.  But is there a beneficial factor in SequelSphere being 100%
>> JavaScript?
>> 
>> Can someone tell me what use SequelSphereDB may have with Node.js?  Why
>> would someone want to use SequelSphere rather than a much more mature
>> server-side native relational database?
>> 
>> Thanks!
>> 
>> john...
>> 
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
> 
> -- 
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: 
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to