Re: [GENERAL] Trouble with RPM

2000-07-17 Thread Jeffrey A. Rhines

BTW, Lamar, thanks for the RPMs.  Fine job.

Lamar Owen wrote:
> 
> Gilles DAROLD wrote:
> > Please don't use RPM if you don't want to have a Win$ based install.
> > It's remember me a very old question: Where are the DLL ?
> 
> > The better way is to get the tarball and do a fresh compilation, you will
> > learn more about postgres (see the INSTALL file and other documentation).
> > And then all your files will go in /usr/local/pgsql by default !
> 
> You know, it's responses like this that make me think... why do I pour
> so much energy in trying to get the RPM's right?  And then I remember
> all those folks that have thanked me for the good RPMs.
> 
> RPMs are in no way comparable to Win.  But, then again, if you want to
> really learn X, or the linux kernel, you should really go do the
> 'roll-your-own-distribution' thing -- not use RedHat at all.
> 
> The RPM's have been built to simply and easily allow things that are not
> easily possible with the standard tarball installation -- such as not
> having the postmaster/backend on a client-only system.  Or picking and
> choosing amongst the clients.  Or not having to have the source taking
> up space after the system is built.  Some folks actually want to run
> PostgreSQL on secure boxen that won't even have a compiler installed --
> such as my production database server.
> 
> And, if you build from source, and put everything in /usr/local/pgsql,
> you have all that added work to get everything working right.  If you
> just simply want to _use_ PostgreSQL to get some work done, then there
> is nothing at all wrong with using the RPM set.
> 
> To answer the original question, refer to the
> /usr/doc/postgresql-7.0.2/README.rpm file -- then install
> postgresql-server RPM.
> 
> As to 'DLL Hell' -- thanks to the way rpm works, you are never in danger
> of this -- rpm -ql package-name gives you a complete list of files in a
> particular rpm.  The companion 'rpm -qf /some/file/some/where' gives you
> the inverse, showing what package a file belongs to.  Of course, you do
> need a recent RedHat distribution -- but you need that anyway.  (I am
> working on getting the source RPM to build on other
> distributions/OS's)
> 
> Comparing the RPM installation to Win is a low blow -- so, yes, it does
> strike a nerve.
> 
> --
> Lamar Owen
> WGCR Internet Radio
> 1 Peter 4:11



[GENERAL] PostgreSQL, ODBC, Access

2000-07-24 Thread Jeffrey A. Rhines

Hello All,

Here's a bothersome issue:  I've got the most recent versions of
Postgres, ODBC client for Win32, and Access 97.  My client can enter new
records fine via a linked table.  However, when she goes back to add
data to a column, she gets the following error:

message box title: "Write Conflict"
description: "This record has been changed by another user since you
started editing it.  If you save the record, you will overwrite the
changes the other user made."
buttons: "Copy to Clipboard" and "Drop Changes".

She is the only person using the database at the time.  The column type
doesn't matter, either.  Does anyone know what causes this?

Best Regards,
Jeff Rhines



[GENERAL] Web front-end

2000-07-24 Thread Jeffrey A. Rhines

It seems i remember seeing somewhere that someone had developed a
generic web front-end to Postgres.  Was this a dream, or has someone
else seen this, too?  If not, would anyone be interested in
collaborating on a JDBC/Java Servlets - based web front end to
Postgres?  By the nature of JDBC and servlets, it would of course be
usable for other RDBMSs as well.  (although i don't know why anyone
wouldn't use PG ;)

Regards,

Jeff



[GENERAL] Asking postgres about existing connections?

2000-08-13 Thread Jeffrey A. Rhines

All,

Is there a way to ask postgres how many connections currently exist, and
who is using them, etc?

Regards,
Jeff



Re: [GENERAL] [Solved] SQL Server to PostgreSQL

2000-08-22 Thread Jeffrey A. Rhines

I've wondered that myself, actually.  What are the benefits and
drawbacks to going with one over the other, besides the obvious 255-char
field length limit for varchar?  The reason to stay away from "memo"
fields in other serious RDBMSs are typically more difficult maintenance,
significantly lower performance, and requiring special function calls to
get the data out.  Do any of those apply to PG?

Jeff

Tom Lane wrote:
> 
> Tressens Lionel <[EMAIL PROTECTED]> writes:
> > Le 22.08.00 a 09:37, "Roderick A. Anderson" m'ecrivait :
> > )I was able to get the table format by using MS Access.  Only question left
> > )is what is the corresponding field type in PostgreSQL for a memo field in
> > )SQL Server/Access (varchar())?
> 
> > 'text' type perhaps ?
> 
> Uh ... what's wrong with varchar(n) ?
> 
> regards, tom lane