On 7-Sep-07, at 8:05 PM, Bart Silverstrim wrote:
>> Neither :)
>> Concurrency control of transactions is what determines if a database
>> is multiuser or not.
>> SQLite is single user (only 1 transaction at a time) regardless of
>> how many people are using it (including REALSQL Server)
>
> So...if the application works with the database in the application as
> designed, then it's okay with RS?
Not sure what you mean
> I would like to try working with an idea I'm kicking around, but I
> don't
> like the idea of designing something that would end up requiring the
> full SQL database in Pro and having a client purchase both the
> application and a license from RS for the database portion. I can't
> find material that clearly defines under what circumstances the
> database
> in Pro vs. Standard would not be suitable for different purposes.
The built in database in standard is stand alone.
No server. The database engine is compiled into your application.
The database in Pro is that way too.
But since Pro can use database plugins you CAN hook it up to a
Database Server like Sybase, Oracle, REAL SQL Server, OpenBase, etc.
Can you communicate between various apps and hack together a "multi
user" set up ?
Sure but you may have some issues.
For low volume stuff it will probably be OK.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|