Re: [Slashcode-development] (no subject)

[Brian A. <br...@ta...>]

Nathan Vonnahme wrote:
> You might look into the patch on the sourceforge bugs page to fix
> extracols support, but it won't exactly do what you want.  It might be
> useful to study, though, since it is doing something similar.
I wouldn't use extracols, it has been dropped in the development schema.
I would make use of getStory() setStory() and let data fall into the
param table.

> [%
> USE Slash;
> 
> # args are: columns, tables, where, other
> sth = Slash.db.sqlSelectMany(
>         'guide.sid, title, section',
>         'stories, guide',
>         "stories.sid = guide.sid AND guide_parent_sid = '$story.sid'",
>         'ORDER BY title'
> );
I have been wondering when it would cross someone's mind that they
can do that.

> Slash::DB has a mockery of documentation in it, you usually have to read
> the code in Slash::DB::MySQL to figure out what the methods do and how to
> call them.
Yeah, I stubbed it out and never did more then a few pieces of it. Time
:)

> I would guess that there is a performance penalty for doing this sort of
> thing in the templates, but there may not be, since the templates are
Probably isn't, but there is another issue to not do it. If you
ever want to move to another database you won't have the ability to
use the abstraction layer to save you porting time. Plus if directly
hit the DB, you may find that in the future your templates
will break because we made some schema change.

	-Brian