Re: [phpBT-dev] MODULES FOR 0.9.0

[John W. <jp...@us...>]

Jirka Pech wrote:
>I want to add table for modules, where will stay project_id as primary key 
 >and columns for use_oses, use_databases, use_environments. These columns
 >will stay as options when creating a project.
>Maybe it will be better to have only four columns (except primary key) 
 >(in two tables): project_id, module, module_table_name and 
module_key_name.
 >We will then check every row with corresponing project_id and use 
modules in
 >these rows. I'm not sure now, but I think it will be better for 
future, if
 >we want users to easily create their's own modules. It's easier to add 
a row
 >than a column to table (and table doesn't have to be off-line when 
adding a row).

I've been thinking the same about adding the user selection of
templates - adding a column for each item is 'quick' to develop but not
as flexible as the 'row' method that I think you are talking of.

The point about not having to take the db off line is a good one -
adding a row to an existing table is really easy because you are simply 
manipulating data in the table whilst adding a column to an existing 
table is slightly more 'risky' as you're altering the structure.
I can't see there's much difference for a new installation, but where an
existing install is being upgraded the row 'method' has to be better...

 From the work I've been doing on the user-based template selection, the
'row' method requires significantly more coding & logic than the
'column' method but once that's done I think it's a more elegant
solution.

> 
> Jirka
> 
> P.S.: Sorry for my english, it's not good, but I'm working on learning it better. 
>Please tell me when I'm saying something wrong.

Hey, no need to apologise... Your English is far far better than my 
Czech.... (or any other European language other than English)

> 
> _______________________________________________________________
> Hundreds of nodes, one monster rendering program.
> Now that's a super model! Visit http://clustering.foundries.sf.net/
> 
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev
>