> Gil: I downloaded PostgreSQL based on the recommendations I received from
> the Dabo group. I don't have the book, but I am using PostgreSQL
> on Windows
>
> I would be interested in the book, though, because all of my development
> will be on Windows.
I just did a Power Read of the PostgreSQL For Windows book. I sure wish I
had this available when I first started to dink around with PostgreSQL last
year! I already flogged my way through a lot of the setup and network
connectivity issues last year, but the installation & setup part of the book
still has some great info. This will be an important part of my Must Have
reference books, just about as important as A Hackers Guide To Visual FoxPro
(still) is.
I know I posted my reasons for moving to PostgreSQL a while ago, and maybe
more than once. My views have not changed all that much, other than a
deeper confidence that I am going in the right direction. My reasons
include:
1) I need a much more scalable database than the 2Gb file size limit I am
coming close to hitting with VFP,
a) VFP View results against PostgreSQL tables must still consume
under 2Gb,
regardless of how large the RDMS table is allowed to grow
2) I wanted a database that will work well over a thin-net or Internet
connection,
a) Remote Views in VFP will do that, but the scalability is still
an issue
3) Despite how simple it is to work in VFP, and have terrific performance,
it has not built in security, more of an issue with Privacy Laws today.
PostGreSQL has built in security,
4) ACID (no, not the kind we used to have around in high school),
PostgreSQL
has it,
5) ODBC and other more recent methods of connectivity (for Java),
6) High performance and great indexing options,
a) Full Text Indexing is available as an add-in during installation
7) Good documentation had to be available, and the RDMS had to be accepted
by a relatively large following,
a) Windows based PostgreSQL could have been better documented
before I got
the book referenced previously, but who wants to go through all the grief of
creating thorough and clear (and easy to find) documentation?
b) Firebird looked interesting, but does not seem as widely
accepted as
PostgreSQL.
8) Low cost or free to End Users with respect to licensing, not costly as
with full M$ SQL Server or Oracle,
a) Unlike MySQL (which I had considered), for commercial use
without
disclosing source code, there is no license fee per server.
b) Not only is it totally free, it is free to alter for those who
feel
compelled to do so (won't be me!)
9) I really wanted an Open Source solution, so the solution I hitch my
future to will not simply be taken away by a software provider that has
decided it is time to put it out to pasture because it is no longer
profitable to market. That said, I am glad VFP will still be viable for
many years, as I plan to use it for some front end solutions while using
PostgreSQL on the back end.
10) Migrateable (sic?) between popular OS platforms. PostgreSQL runs under
Windows, Linux and Unix. Tables can be imported/exported between files
residing under these different OSes. And, non-PostgreSQL records can be
imported from various formats.
For my time investment I feel PostgreSQL is the clear choice given my
environment. I will likely always need to remain in the World of Windows
for my apps, but my back end server can be Linux or Windows. Windows will
always cost more for the OS plus the CAL fees than a similar Linux machine.
A great server solution is looking more and more like a Linux Host OS,
running VMWare Server (free) with Windows 2000 Pro or XP Pro as a Guest OS
for those programs that must run in Windows (I have a few of them, VFP <g>,
ProComm). PostgreSQL can be on the Linux Host OS, allowing network
connectivity with no CAL license fees, yet great connectivity to the
database through the network connections or the Guest OS under VMWare. Next
world to delve into, Dabo and Python. More time, more time, does anybody
know what happened to my Day Stretcher?
Gil
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jeff Johnson
> Sent: Tuesday, April 03, 2007 5:13 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Another life after VFP thread? PostgreSQL for Windows book
> justhit the market
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > On Behalf Of mrgmhale
> > Sent: Tuesday, April 03, 2007 1:36 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Another life after VFP thread? PostgreSQL for Windows book
> > justhit the market
> >
> > So, in case anyone else is interested in the book (Whil, are
> you going to
> > put it into your offerings?), the title is "PostgreSQL 8 For Windows",
> > written by Richard Blum. If Whil is going to offer it (hint,
> hint), then
> > that is who we ought to consider purchasing through. In any
> event, it is
> > now available.
> >
> >
> > Gil
> >
>
> Gil: I downloaded PostgreSQL based on the recommendations I received from
> the Dabo group. I don't have the book, but I am using PostgreSQL
> on Windows
> and I am totally surprised and pleased at the server. I has an
> "Enterprise
> Manager" type thingy that it comes with that is much easier to understand
> (and therefore use) than MSSQL. It was easy to set up and if you have any
> questions, there is literally tons of help out there.
>
> I would be interested in the book, though, because all of my development
> will be on Windows.
>
> Jeff
>
> Jeff Johnson
> [EMAIL PROTECTED]
> 623-582-0323
> Fax 623-869-0675
>
>
>
> --- StripMime Report -- processed MIME parts ---
> multipart/signed
> text/plain (text body -- kept)
> application/x-pkcs7-signature
> ---
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
