Paul M Foster <[EMAIL PROTECTED]> wrote:
> I'm doing some massive (internal company) applications using PHP, which
> query extensive PostgreSQL tables. This is fine, but obviously it often
> requires multiple web pages to get something done. Supposedly, AJAX
> promises to make web pages more int
Dave Page wrote:
> > GnuTLS is LGPL, which isn't quite as liberal as postgresql's
> > license, but should still be ubiqutous enough to be worthwhile.
>
> The note on the fsf directory (http://directory.fsf.org/gnutls.html) is a
> little off-putting:
>
> "The program is currently in developm
Martijn van Oosterhout wrote:
> Well, it's a Debian problem that possibly applies to Linux distrubutors
> in general. Here is a good write up:
>
> http://www.gnome.org/~markmc/openssl-and-the-gpl.html
>
> The issue is that while anybody else can take advantage of the
> "components usually part o
Chris Travers <[EMAIL PROTECTED]> wrote:
> > I'd call that the short term solution, with the long term solution
> >being to finally convince the right people to remove that clause from
> >OpenSSL's license.
> As I have said before, I think it is Debian's problem at least from the
> perspectiv
Martijn van Oosterhout wrote:
> To save you some time: this has been rehashed on the OpenSSL lists and
> the conclusion is basically:
>
> 1. It's not a problem, it's the GPLs problem
> 2. It doesn't appear they can change the licence for some reason
>
> We are not the first people to run into th
Stephen Frost <[EMAIL PROTECTED]> wrote:
> GPL-licensed software depending on a BSD-licensed package *isn't* a
> problem. If we didn't link Postgres w/ OpenSSL this wouldn't be any
> issue at all. If the freeradius authors explicitly say they don't have
> a problem linking against a BSD-with-adve
Scott Marlowe <[EMAIL PROTECTED]> wrote:
> > >> I don't feel it's a questionable reading of the GPL at all. In fact,
> > >> it's pretty clear and I'm about 99% sure the FSF has commented on this
> > >> as well. It's true that it's unlikely anyone would actually sue Debian
> > >> over it but that
Chris Travers <[EMAIL PROTECTED]> wrote:
> My own opinion is this: The Debian crowd are often technical enough
> they can build whatever they want from source. Debian is a niche
> distribution and not something we should spend too much time worrying
> about whether our software can be indirect
Alan DeKok <[EMAIL PROTECTED]> wrote:
> > It appears that several other GPL apps have added a special clause
> > to their license that allows them to be linked against OpenSSL.
> >
> > Could this be done for freeradius/freeradius-postgresql as well?
>
> I have no objection to that.
>
> D
Scott Marlowe <[EMAIL PROTECTED]> wrote:
> > GPL partisans feel that BSD-with-advertising-clause is not compatible
> > with the GPL. I think the sticking point here is that openssl is using
> > an advertising clause.
>
> But the way Douglas' message read, it was only GPL packages that should
> be
Greetings FreeRadius people,
This discussion started on the postgresql's "pgsql-general" mailing
list. The problem here is that the freeradius-postgresql package needs to
link against libpgsql, which means that it may be indirectly linked against
openssl. There is a conflict between OpenSS
lmyho <[EMAIL PROTECTED]> wrote:
> > Oh right, they're claiming that they can't distribute freeradius using
> > postgresql because postgresql links to OpenSSL. freeradius is GPL which
> > makes for an incompatabilty. Not something PostgreSQL is responsible
> > for, given Debian could compile withou
Martijn van Oosterhout wrote:
> On Thu, Apr 06, 2006 at 10:27:36AM -0700, lmyho wrote:
> > After desperately checking, we were told that debian doesn't distribute the
> > binary
> > module of freeradius for postgresql because of the incompatible license of
> > these two
> > apps! However we can
I have a DTD that I want to convert into a database schema. (For the
curious, it's the XML DTD for Kismet's XML output; see
http://www.kismetwireless.net/ and
http://kismetwireless.net/kismet-3.1.0.dtd). After converting it to a W3C
XML schema, it looks like it has the sort of infroamtion that is n
Stephen Frost <[EMAIL PROTECTED]> wrote:
> > Speaking of Debian, is there some list to discuss Debian-specific
> > packaging issues, e.g. how to create a Debian package which installs
> > some stored procedures written in C?
>
> Sure:
> http://lists.alioth.debian.org/mailman/listinfo/pkg-postgresq
Merlin Moncure <[EMAIL PROTECTED]> wrote:
> On 2/3/06, Tyler MacDonald <[EMAIL PROTECTED]> wrote:
> > I've been wondering, does anybody know which is more likely to be
> > installed on a postgresql server? Which is faster? I'm writting an
> > a
Uwe C. Schroeder <[EMAIL PROTECTED]> wrote:
> Probably because the notice you see is a notice from the database engine,
> not from the driver.
OK, but in order for them to get to my tty, they have to bubble down
from postgres, through the UNIX/TCP socket I am talking to the driver with,
I'm using the DBD::Pg driver and i've specifically turned "PrintWarn" off,
yet I am still getting spammed with messages like this:
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "aus_flag_pkey"
for table "aus_flag"
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"a
Hey,
I was puzzling over how to make sure a database has plpgsql
installed in it in pure SQL. I felt this would simplify the schema's
installation process since calling of extra binaries is no longer
neccessary. Here's what I came up with:
CREATE OR REPLACE FUNCTION make_plpgsql () RETUR
I've been wondering, does anybody know which is more likely to be
installed on a postgresql server? Which is faster? I'm writting an
application in perl that is going to need to get broad information about
heiarchial data (how many parents, settings common on parents, etc), and I'd
like to
Apache::DBI claims that it will reconnect to a database if it's gone away.
DBD::Pg claims that it supports the ping method. However, when I restart my
database server while apache2 is running, all mod_perl pages that are
database driven return internal server errors, no matter how many times I
refr
Hi,
You probably want something like "COPY table_name FROM STDIN";
here's an example from a table that defines flags:
COPY auth_flag (id, name, description) FROM stdin;
2 Admin System Administrator Access
4 New PasswordUser must change password on next login
8 Super
Will Glynn <[EMAIL PROTECTED]> wrote:
> Postgres completely for a few seconds didn't lower the number. It wasn't
> taken by any process, which leads me to believe that it's a kernel bug.
If it was a shared memory segment allocated a particular way (I
*think* it's "shm_open", I'm not 100%
Jaime Casanova <[EMAIL PROTECTED]> wrote:
> >Either way the end result is that some database drivers poison a
> > transaction if there's any error, others are selective about which errors
> > are fatal and which are not, and still others just don't care at all.
> that is a mis-conception...
Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> The inconvenience I'll grant, but the non-standard claim I think
> needs some justification. When the database encounters an error in a
> transaction, it is supposed to report an error. An error in a
> transaction causes the whole transaction to fail:
Tim Bunce <[EMAIL PROTECTED]> wrote:
> I'll guess that what you're really after is to be able to call begin_work
> again whilst an earlier begin_work is in effect and have the DBI keep a
> counter of how deeply nested the begin_work calls are. Then commit would
> decrement the counter and only comm
26 matches
Mail list logo
