I have this code that records pwords in the DB .. kind of securely:
https://github.com/matiu2/witty-plus/blob/master/base-app/model/User.hpp
It just stores a SHA of the password.
But I also have this ticket to upgrade it:
https://github.com/matiu2/witty-plus/issues/7
And this other project that does it better than me (but not better than my
planned one ;) -
https://bitbucket.org/starius/thechess/src/0ae7a62861b8/src/model/User.cpp
In regards to the MySQL vs Postgres Holy war that some guy in this thread
started...
Back in the 90's we had a project that was receiving around 1,000,000
insertions a week, and generating a lot of reports. Originally mysql, mysql
died (as in completely crashed) when trying to run reports (around the 8
million row time). We switched to MSSQL, which managed to crash the entire
machine it was hosted on when running reports. We tried Oracle, but cost
became prohibitive. System runs nicely with Postgresql, and last I checked
had like 160 million rows in the horriblest table (with cron jobs to do
hourly propogation of the records into summary tables).
Anyway, since then, I've always used Postgresql and never found a job it
couldn't handle. I even had a brief affair with couchdb, mongodb, and that
other one, but came back to PostgreSQL. In my work (support in a hosting
company) I see a bunch of MySQL errors on production sites every day
(usually from lack of attention to the DB). I always sigh to myself, and say
.. aw, that'd be so quick to fix in PostgreSQL.
For example the explain command; postgresql's give you so much more useful
information:
EXPLAIN SELECT sum(i) FROM foo WHERE i < 10;
QUERY PLAN
---------------------------------------------------------------------
Aggregate (cost=23.93..23.93 rows=1 width=4)
-> Index Scan using fi on foo (cost=0.00..23.92 rows=6 width=4)
Index Cond: (i < 10)
vs MySQLs:
mysql> explain extended select * from sbtest where id>5 and id>6 and
c="a" and pad=c;
+----+-------------+--------+-------+---------------+---------+---------+------+--------+-------------+
| id | select_type | table | type | possible_keys | key |
key_len | ref | rows | Extra |
+----+-------------+--------+-------+---------------+---------+---------+------+--------+-------------+
| 1 | SIMPLE | sbtest | range | PRIMARY | PRIMARY | 4
| NULL | 422510 | Using where |
+----+-------------+--------+-------+---------------+---------+---------+------+--------+-------------+
1 row in set, 1 warning (0.02 sec)
That's my 2c. :)
Let the Holy war continue or end .. but let's get something out of it please
:)
On Thu, Oct 20, 2011 at 2:00 AM, Bartyik Péter <kennyngs...@gmail.com>wrote:
> Thanks for the advice, I think I will go with MySql as database (I'm not
> familiar with Wt::Dbo at all, also not sure how to store passwords securely
> at Wt::Dbo), Wt(C++) and Apache as webserver, thoughts?
>
> On Wed, Oct 19, 2011 at 5:49 PM, Pau Garcia i Quiles <
> pgqui...@elpauer.org> wrote:
>
>> Hi,
>>
>> WtRuby is quite outdated (Wt 2.x), so go for either JWt (Java) or Wt (C++)
>>
>>
>> 2011/10/19 Bartyik Péter <kennyngs...@gmail.com>
>>
>>> although now that you mention, I wonder which one do you recommend,
>>> standard Wt, or WtRuby?
>>>
>>>
>> --
>> Pau Garcia i Quiles
>> http://www.elpauer.org
>> (Due to my workload, I may need 10 days to answer)
>>
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2d-oct
>> _______________________________________________
>> witty-interest mailing list
>> witty-interest@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/witty-interest
>>
>>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> witty-interest mailing list
> witty-interest@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
>
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Ciosco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
