Re: [Pagekit-devel] contribute: pkit_setup_db.pl, a more generic pkit_setup_sqlite_dbfile.pl

[<pdu...@so...>]

Hi Boris,


> Ok, I change the output.

I had a look at the diff and it looks Ok, but I have some requests:

I simulated the error and got the following output:
=== begin ===
one or more tables exists already.
For security reason we do not overwrite it.
=== end ===

I'll change this to read:
=== begin ===
One or more tables already exist.
For security reasons they will not be overwritten.
=== end ===

BTW, this is of course technically wrong, as no database (that I know of)
will allow you to create a table if it already exists.

> I attach the current version of pkit_setup_db.pl not tested so far.

Ok, only if you add your name to the "AUTHOR" section :).

> Im unsure if this is the way to go, pagekit is a very powerfull system, the 
> users have already more or less experience with databases, apache and perl 
> for large applications. They just need to know what to do, not something that 
> do something that satisfy most users. Every PageKit user is already a 
> developer.

You have a better feeling for this, I agree.

What I wanted to show in the demo, is how an application can be built
that is "completely database-type independent". Database-type
dependency is something that stops most potential developers from
using a certain package. If it is in the demo, it will impress people
(even hard core, large-site guys), I think. Just consider the
following fact: Bricolage == postgres and Krang == mysql

Whatever, the demo is probably good enough as it is.

> What I mean is we need a better beginner tutorial with a pagekit-cookbook ;-).
> And a better understanding of errors that can occur while trying A::P.

Yes, I admit, that would have helped me too ;-). I you want to, I'll
help you with something like this.

cu
--
Pieter