On Fri, Dec 16, 2011 at 3:28 AM, Scott Marlowe wrote:
> Debian / Ubuntu will release an updated pg pacakge days after a new
> postgresql minor version comes out, but php? It can be months or
> years before a new minor version gets the go ahead
The beauty of modern open source project management
On Thu, Dec 15, 2011 at 1:58 AM, Bèrto ëd Sèra wrote:
> My main problem with PHP is that it has loads of issues upon changing
> versions, there are a lot of applications based on it, and sooner or later
> you bump into having one application in need for one version and another
> being unable to r
On Thu, Dec 15, 2011 at 1:49 AM, Andreas wrote:
> Am 15.12.2011 05:47, schrieb Darren Duncan:
>
>> Darren Duncan wrote:
>>>
>>> A practice I like that I've seen done for a federal-government scale
>>> database program is to have each person using the application to login to
>>> the database using
Am 15.12.2011 05:47, schrieb Darren Duncan:
Darren Duncan wrote:
A practice I like that I've seen done for a federal-government scale
database program is to have each person using the application to
login to the database using their own temporary database user. How
it works is that the databa
Hi!
> To be fair, isn't that an argument against whatever the popular
> programming language is of the day? I mean, we can all remember
> Matt's Scripting Archive and Perl.
>
If I can add a personal opinion, my main reason to avoid PHP is not related
to programmers at all. There are loads o
On Thu, Dec 15, 2011 at 4:23 PM, Chris Travers wrote:
> So the problem is hardly limited to PHP.
Oh, it definitely is not. Really, it's a problem with human beings who
think they're programmers. It just seems to occur more frequently in
some languages than others.
ChrisA
--
Sent via pgsql-gene
On Wed, Dec 14, 2011 at 8:14 PM, Chris Angelico wrote:
>> In my opinion, that's a pretty elitistic view. Certainly, that's one way of
>> writing PHP, but it isn't the only one. Quite a few of us have started with
>> something like what you've outlined here, but have long ago moved on to more
>> m
Darren Duncan wrote:
A practice I like that I've seen done for a federal-government scale
database program is to have each person using the application to login
to the database using their own temporary database user. How it works
is that the database has a users table similar to as if the app
A practice I like that I've seen done for a federal-government scale database
program is to have each person using the application to login to the database
using their own temporary database user. How it works is that the database has
a users table similar to as if the application was managing
On Thu, Dec 15, 2011 at 11:25 AM, Leif Biberg Kristensen
wrote:
> Onsdag 14. desember 2011 22.21.04 skrev Chris Angelico :
>> The biggest problem with PHP, imho, is actually that it's so easy to
>> use. Anyone can get a WYSIWYG editor, save as HTML, and have a web
>> page... and then all you need
Em 14/12/2011 22:25, Leif Biberg Kristensen escreveu:
Onsdag 14. desember 2011 22.21.04 skrev Chris Angelico :
The biggest problem with PHP, imho, is actually that it's so easy to
use. Anyone can get a WYSIWYG editor, save as HTML, and have a web
page... and then all you need to do is rename i
On 12/15/2011 01:16 AM, Andreas wrote:
Am 14.12.2011 14:28, schrieb Craig Ringer:
On 14/12/2011 8:32 PM, Andreas wrote:
Hi,
I asked elsewhere about the best way to store db credentials within
a user-session of a web-app.
Where? Link?
Well, it was on the general list of php.net.
I read yo
This is somewhat of a diversion but
On Wed, Dec 14, 2011 at 4:25 PM, Leif Biberg Kristensen
wrote:
> Onsdag 14. desember 2011 22.21.04 skrev Chris Angelico :
>> The biggest problem with PHP, imho, is actually that it's so easy to
>> use. Anyone can get a WYSIWYG editor, save as HTML, and hav
Onsdag 14. desember 2011 22.21.04 skrev Chris Angelico :
> The biggest problem with PHP, imho, is actually that it's so easy to
> use. Anyone can get a WYSIWYG editor, save as HTML, and have a web
> page... and then all you need to do is rename it to ".php" and put
> some special tags in it, and l
On Wed, 14 Dec 2011, Andreas wrote:
Hi,
I asked elsewhere about the best way to store db credentials within a
user-session of a web-app.
You might give this a read:
http://database-programmer.blogspot.com/2009/02/comprehensive-database-security-model.html
It goes through how using a DB use
On Thu, Dec 15, 2011 at 4:16 AM, Andreas wrote:
> Well, it was on the general list of php.net.
> I read your link and understood your not a particular fan of PHP.
> I'm not exactly dogmatic about PHP either. It's just the first approach to
> the web-app topic for me. One has to start somewhere.
Am 14.12.2011 14:28, schrieb Craig Ringer:
On 14/12/2011 8:32 PM, Andreas wrote:
Hi,
I asked elsewhere about the best way to store db credentials within a
user-session of a web-app.
Where? Link?
Well, it was on the general list of php.net.
I read your link and understood your not a partic
Andreas wrote:
> I asked elsewhere about the best way to store db credentials within a
> user-session of a web-app.
>
> It appeared that it was for everybody but me evident that instead of
> heaving a db-role+passwd for every user of an application it was better
> to have just 1 set of db-credenti
On Wed, Dec 14, 2011 at 4:32 AM, Andreas wrote:
> Hi,
>
> I asked elsewhere about the best way to store db credentials within a
> user-session of a web-app.
>
> It appeared that it was for everybody but me evident that instead of heaving
> a db-role+passwd for every user of an application it was b
On 14/12/2011 8:32 PM, Andreas wrote:
Hi,
I asked elsewhere about the best way to store db credentials within a
user-session of a web-app.
Where? Link?
It appeared that it was for everybody but me evident that instead of
heaving a db-role+passwd for every user of an application it was
bet
Hi,
I asked elsewhere about the best way to store db credentials within a
> user-session of a web-app.
> It appeared that it was for everybody but me evident that instead of
> heaving a db-role+passwd for every user of an application it was better to
> have just 1 set of db-credentials for the app
Hi,
I asked elsewhere about the best way to store db credentials within a
user-session of a web-app.
It appeared that it was for everybody but me evident that instead of
heaving a db-role+passwd for every user of an application it was better
to have just 1 set of db-credentials for the appli
22 matches
Mail list logo
