I agree those options are better..unfortunately, every field is in use
except the score, view and print fields. The db structure is uneven there is
a single subtopic for each department but then some have another subtopic
for the year and some do not...maybe the solution though is to force
everyone to have the second subtopic for year and then get the topicname of
the parent for the subtopic....actually not as bad as it sounds....
I actually was programming in my sleep...literally...and came up with a way
to shuffle everything around to make it click....but I like your idea
better....
Thanks!
> -----Original Message-----
> From: Tarjei Huse [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 24, 2001 3:57 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [midgard-user] PHP overhead sort of question...
>
>
> Hi,
>
> I think you got at least two options that are better, a) are the type and
> extra fields all in use?
> 2. Why not make a topic for reach departmen and run
> mgd_list_articles_all to
> get the subtopics?
> 3. BTW It should not be to much work to sort the existing arts into
> subtopics.
> 4. I you already have plaved the departments in subtopics, then you can do
> mgd_list_art_all(topic1)
>
> topic1
> |-dep1
> |-dep2
> |-dep3
> etc
>
> and then use the topic id in each art to do the rest.
>
> 5. You could also use parameters nadmin has very nice support for em.
>
> Tarjei
>
> > My second question for the day....I have articles which come
> > out 8 at a time and are associated with one of 23 different departments.
> > Right now I just put the department name in the name field and
> spit it out
> > when the article is gotten...ALL of the other fields in the
> record are in
> use
> > except the score. I need the name field for something else so I was
> > thinking of seting the score = 1-23 and then running a sort of
> innefficient
> > if/then/elseif statement to conect the score (key number) to the right
> string to spit
> > back...it seems like a crappy way to do it but I can't make
> anything come
> > out of my "needs a vacation" head. Is this as inefficient as
> I think? Is
> > there a better way to do it....I have this huge nagging feeling I am
> missing
> > something really obvious, but that same nag won't tell me what a better
> way
> > to do it is ....
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
