[isf-wifidog] MySQL support - shouldn't we skip it?

[Matthew Asham]

I don't see any reason why MySQL support should still be in it.  Nuke it.


 

> -----Original Message-----
> From: wifidog-bounces at listes.ilesansfil.org 
> [mailto:wifidog-bounces at listes.ilesansfil.org] On Behalf Of 
> Max Horváth
> Sent: January 22, 2006 10:47 AM
> To: WiFiDog Captive Portal
> Subject: Re: [isf-wifidog] MySQL support - shouldn't we skip it?
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> So, what say others?
> 
> Shall we remove MySQL for now?
> 
> Cheers, Max!
> 
> Am 21.01.2006 um 07:37 schrieb François Proulx:
> 
> > I'm OK, as long as you don't use highly specific non-SQL99 /  
> > SQL2003 commands. Can anybody confirm that the new PHP PDO 
> supports  
> > BLOB encapsulation for Postgresql ? And I don't mean BYTEA fields,  
> > I'm referring to OID-based BLOBs. We'd have to modify some SQL  
> > generation logic for using PDO's prepared statements, but that  
> > should be trivial in most cases, althought since its critical and  
> > it has to be done carefully ...
> >
> > I'm all for not taking care of MySQL too much, but with MySQL 5.0  
> > plenty of things have changed ... it will be more and more trivial  
> > to support it I guess. For 1.0, let's forget it. But moving to PHP  
> > PDO is always a good thing, if only for preventing SQL Injection  
> > with prepared statements. I haven't analyzed all our code , but  
> > just escaped strings might not be enough... ie. 
> $user_id="0; DELETE  
> > FROM users" ....  "SELECT * FROM users WHERE user_id =  
> > {$user_id};"    So, we might be vulnerable where we use integers  
> > fields. PDO's prepared statement take care of this by 
> escaping semi- 
> > colons, adding single quotes on integer fields etc...
> >
> > On 20-Jan-2006, at 19:35 , Max Horváth wrote:
> >
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Hi everybody ...
> >>
> >> before we'll release WiFiDog 1.0 I think that we should decide  
> >> whether to support MySQL or not.
> >>
> >> In my opinion we should skip the support and concentrate on  
> >> PostgreSQL ... I mean - we can't release a WiFiDog 1.0 release  
> >> with broken MySQL support, right? ;)
> >>
> >> For more than one year there hasn't been found a maintainer for  
> >> MySQL. And it never really worked.
> >>
> >> I think it be much better to skip support and to add some 
> advanced  
> >> techniques that can only be done in PostgreSQL and that would  
> >> speed up WiFiDog.
> >>
> >> What's your opinion?
> >>
> >> Cheers, Max!
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v1.4.1 (Darwin)
> >>
> >> iD8DBQFD0YG/+BKgC+eQ3ooRApDWAJ9rRByrgtKo9TfUEFE5ppEUivvA3ACgkz/W
> >> ZsJDOKMHPqvUq9pTtvP+4F0=
> >> =TUXV
> >> -----END PGP SIGNATURE-----
> >> _______________________________________________
> >> WiFiDog mailing list
> >> WiFiDog at listes.ilesansfil.org
> >> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
> >
> > _______________________________________________
> > WiFiDog mailing list
> > WiFiDog at listes.ilesansfil.org
> > http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
> >
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
> 
> iD8DBQFD09M8+BKgC+eQ3ooRAuZyAJ93miMhFv9aweJE1VxOnWEVknySIwCfV+/r
> jKol0AJlwT7NCMZrqxdDuLU=
> =0LBq
> -----END PGP SIGNATURE-----
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog