On Mon, Apr 24, 2006 at 08:54:40PM -0400, Paul Malcher wrote:
> On 4/24/06, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
> >
> > Keep in mind, there's *WAY* more Windows users than Linux users; that
> > doesn't mean Windows is a better OS.
>
>
> Indeed also keep in mind both Postgres and MySQL are
On 4/24/06, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
>
> Keep in mind, there's *WAY* more Windows users than Linux users; that
> doesn't mean Windows is a better OS.
Indeed also keep in mind both Postgres and MySQL are cross platform as well.
One final thought: the support you'll be able to get
On Thu, Apr 06, 2006 at 04:58:43AM -0700, Lenster wrote:
> 1) Googling PostgreSQL produced 52,700,000 hits, Googling MySQL produced
> 397,000,000 hits
I'd be much more concerned with the 'hits' you'll find at
http://sql-info.de/mysql/gotchas.html ...
Keep in mind, there's *WAY* more Windows
My first thought when you asked this: If you have to ask, just go with
MySQL. If for no other reason than to ease learning. As you said
before, Googling for each has way different results. I have found
that learning how to do things (with PHP in my case) with Mysql was
easy just because there
Hi Len,
The question you are asking is "loaded". Stay with the ansi SQL statements
that SQLite supports and you will be okay. If you need to use the SQLite
extensions now, you will have to write a "translator" in future - not too
difficult. For an experienced programmer (which you will be if the
Provided your new database has the features you are using it is simple.
For example we use Sqlite and PostgreSQL and transferring between them
is simple. Even the application program API is similar so a conditional
compile in the programs takes care of that and links appropriately.
JS
Thanks Dennis, that's great news - I shall give it a try :-)
--
View this message in context:
http://www.nabble.com/Most-appropriate-Web-based-database-%28Newbie%29-t1404628.html#a3793176
Sent from the SQLite forum at Nabble.com.
Sounds like an interesting setup! Maybe off topic, but, would you care
to elaborate on that topic? Server configuration, virtualization
software running, etc.?
[EMAIL PROTECTED] wrote:
Lenster <[EMAIL PROTECTED]> wrote:
The application needs to be available to about twenty users on a daily
Lenster wrote:
I would like to know whether - at some point in the future should it be
necessary - I could convert my entire SQLite databases including tables etc
to another RDMS such as MySQL? Is this straightforward or convoluted?
The .dump command in the sqlite shell will dump your
Thanks for your reply Richard
After further Googling and reading the replies I've received here I am
coming around to the idea that SQLite probably is the best choice.
I would like to know whether - at some point in the future should it be
necessary - I could convert my entire SQLite databases
Lenster <[EMAIL PROTECTED]> wrote:
>
> The application needs to be available to about twenty users on a daily
> basis, with most of those users making no more than five 'write'
> transactions a day, and around twenty 'read' transactions a day.
>
The SQLite website is itself backed by SQLite.
Sqlite works very well for web applications unless they are large and
very busy. It is easy to manage and backup and performs well.
For a larger scale operation PostgreSQL would be a better choice than
MySql. If you design your application with care you could switch from
Sqlite to
2006 6:59 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Most appropriate Web based database? (Newbie)
>
>
>
> Thanks Guys
>
> I appreciate the input.
>
> >Denis Sbragion
> >how critical and complex is the data stored?
> Well the data IS c
Hello Len,
On Thu, April 6, 2006 13:58, Lenster wrote:
> 1) Googling PostgreSQL produced 52,700,000 hits, Googling MySQL produced
> 397,000,000 hits
...
well, this is quite a poor comparison. On the Internet there are many articles
comparing MySQL vs PostgreSQL vs other database engines. As a
Thanks Guys
I appreciate the input.
>Denis Sbragion
>how critical and complex is the data stored?
Well the data IS critical but NOT complex
>Gerhard Häring
>From what you have said Gerhard it seems that SQLite is probably upto the
job, however MySQL or PostgreSQL will be more futureproof
Lenster wrote:
I am investigating which would be the most appropriate RDMS to use for
a new Intranet based application. I have rounded down my choice to two
candidates - SQLite and MySQL.
Ok. I think that PostgreSQL and Firebird are almost always better
choices than MySQL for a database
Hello Len,
On Thu, April 6, 2006 10:49, Lenster wrote:
...
> Would I be correct in assuming that MySQL is a safer (longterm) bet?
how critical and complex is the data stored? If it's fairly critical and/or
complex (many tables with relations between them) PostgreSQL may be an even
better
Hi Lenster,
For a Web application you are probably better off with MySQL, it runs as
a seperate process and handles multiple threads really well. I'm
probably going to offend the sqlite people out there, but sqlite is
fantastic for an embedded database, and a web app is not what I would
call
I am investigating which would be the most appropriate RDMS to use for
a new Intranet based application. I have rounded down my choice to two
candidates - SQLite and MySQL.
The application needs to be available to about twenty users on a daily
basis, with most of those users making no more
19 matches
Mail list logo
