to use or not to use a database for an archivable and searchable document

**Matthias Gutfeldt** · Jul 17 '05, 03:58 AM

Re: to use or not to use a database for an archivable and searchabledocum ent

Alexandre Plennevaux wrote:[color=blue]
> hello mates,
>
> my question is such: should i turn a 80 pages doc file into a database
>
> The document could be described like this: it is a series of articles
> organised in 2 levels: sections and subsections.
> The user should be able to modify/erase/add articles , subsections and
> sections and still keep the original article inside an archive.[/color]

Sounds like a wiki to me! IIRC there are PHP-based wikis available.

Matthias

**Savut** · Jul 17 '05, 03:58 AM

Re: to use or not to use a database for an archivable and searchable document

I would definitively use a database as it's faster to search for something
in the database than open each html file then search on all the files on a
specific section of the code (strip html tags, etc.). Coding is also easier.
Just think if someone search for "javascript exemple" and you have some JS
also on your page but not in the news, you will have to make lot of
traitments that would be like a piece of cake in a database. This is like
digging a swimming pool with a spoon.

Savut

"Alexandre Plennevaux" <alexandre@la b-au.com> wrote in message
news:4046003c$0 $13866$ba620e4c @news.skynet.be ...[color=blue]
> hello mates,
>
> my question is such: should i turn a 80 pages doc file into a database so
> that:
>
> - i can make it searchable through an online form
> - it can be modified and every modification archives the previous version,
> inside an "archive" table.
>
> ??
>
> The document could be described like this: it is a series of articles
> organised in 2 levels: sections and subsections.
> The user should be able to modify/erase/add articles , subsections and
> sections and still keep the original article inside an archive.
>
> The search system should cover both the current version and the archives.
>
> I get confused on how to organize the whole database system.
> I figured out that maybe it would be better to generate html files out of
> the database content (since it is not going to be changed everyday) and[/color]
then[color=blue]
> perform the search on these html files. Same for the archives. Every[/color]
updates[color=blue]
> generates a new set of html files containing the whole document.
>
> what do you think ?
>
> i need experimented advise here. please help !!
>
>[/color]

**Alexandre Plennevaux** · Jul 17 '05, 03:58 AM

Re: to use or not to use a database for an archivable and searchable document

thanks for your reply. I think i'm going for a mixed solution:

i will have a database holding the content. Everytime the admin modifies the
content, i will have the script generate new html files and update the
database with those files, so the search will look in the database and
return the html file(s) as links (much like google).
this will limit database access as it will not be updated everyday so...
my question is now how to implement the archival logic ?

alex

"Savut" <webki@hotmail. com> wrote in message
news:6Ro1c.1564 4$qA2.768850@ne ws20.bellglobal .com...[color=blue]
> I would definitively use a database as it's faster to search for something
> in the database than open each html file then search on all the files on a
> specific section of the code (strip html tags, etc.). Coding is also[/color]
easier.[color=blue]
> Just think if someone search for "javascript exemple" and you have some JS
> also on your page but not in the news, you will have to make lot of
> traitments that would be like a piece of cake in a database. This is like
> digging a swimming pool with a spoon.
>
> Savut
>
> "Alexandre Plennevaux" <alexandre@la b-au.com> wrote in message
> news:4046003c$0 $13866$ba620e4c @news.skynet.be ...[color=green]
> > hello mates,
> >
> > my question is such: should i turn a 80 pages doc file into a database[/color][/color]
so[color=blue][color=green]
> > that:
> >
> > - i can make it searchable through an online form
> > - it can be modified and every modification archives the previous[/color][/color]
version,[color=blue][color=green]
> > inside an "archive" table.
> >
> > ??
> >
> > The document could be described like this: it is a series of articles
> > organised in 2 levels: sections and subsections.
> > The user should be able to modify/erase/add articles , subsections and
> > sections and still keep the original article inside an archive.
> >
> > The search system should cover both the current version and the[/color][/color]
archives.[color=blue][color=green]
> >
> > I get confused on how to organize the whole database system.
> > I figured out that maybe it would be better to generate html files out[/color][/color]
of[color=blue][color=green]
> > the database content (since it is not going to be changed everyday) and[/color]
> then[color=green]
> > perform the search on these html files. Same for the archives. Every[/color]
> updates[color=green]
> > generates a new set of html files containing the whole document.
> >
> > what do you think ?
> >
> > i need experimented advise here. please help !!
> >
> >[/color]
>[/color]

**Savut** · Jul 17 '05, 03:59 AM

Re: to use or not to use a database for an archivable and searchable document

why not use your solution, create static html page from the database, but
the search would still be done in the database then return the html page,
just like you said.

Savut

"Alexandre Plennevaux" <alexandre@la b-au.com> wrote in message
news:40465d1a$0 $775$ba620e4c@n ews.skynet.be.. .[color=blue]
> thanks for your reply. I think i'm going for a mixed solution:
>
> i will have a database holding the content. Everytime the admin modifies[/color]
the[color=blue]
> content, i will have the script generate new html files and update the
> database with those files, so the search will look in the database and
> return the html file(s) as links (much like google).
> this will limit database access as it will not be updated everyday so...
> my question is now how to implement the archival logic ?
>
> alex
>
>
> "Savut" <webki@hotmail. com> wrote in message
> news:6Ro1c.1564 4$qA2.768850@ne ws20.bellglobal .com...[color=green]
> > I would definitively use a database as it's faster to search for[/color][/color]
something[color=blue][color=green]
> > in the database than open each html file then search on all the files on[/color][/color]
a[color=blue][color=green]
> > specific section of the code (strip html tags, etc.). Coding is also[/color]
> easier.[color=green]
> > Just think if someone search for "javascript exemple" and you have some[/color][/color]
JS[color=blue][color=green]
> > also on your page but not in the news, you will have to make lot of
> > traitments that would be like a piece of cake in a database. This is[/color][/color]
like[color=blue][color=green]
> > digging a swimming pool with a spoon.
> >
> > Savut
> >
> > "Alexandre Plennevaux" <alexandre@la b-au.com> wrote in message
> > news:4046003c$0 $13866$ba620e4c @news.skynet.be ...[color=darkred]
> > > hello mates,
> > >
> > > my question is such: should i turn a 80 pages doc file into a database[/color][/color]
> so[color=green][color=darkred]
> > > that:
> > >
> > > - i can make it searchable through an online form
> > > - it can be modified and every modification archives the previous[/color][/color]
> version,[color=green][color=darkred]
> > > inside an "archive" table.
> > >
> > > ??
> > >
> > > The document could be described like this: it is a series of articles
> > > organised in 2 levels: sections and subsections.
> > > The user should be able to modify/erase/add articles , subsections and
> > > sections and still keep the original article inside an archive.
> > >
> > > The search system should cover both the current version and the[/color][/color]
> archives.[color=green][color=darkred]
> > >
> > > I get confused on how to organize the whole database system.
> > > I figured out that maybe it would be better to generate html files out[/color][/color]
> of[color=green][color=darkred]
> > > the database content (since it is not going to be changed everyday)[/color][/color][/color]
and[color=blue][color=green]
> > then[color=darkred]
> > > perform the search on these html files. Same for the archives. Every[/color]
> > updates[color=darkred]
> > > generates a new set of html files containing the whole document.
> > >
> > > what do you think ?
> > >
> > > i need experimented advise here. please help !!
> > >
> > >[/color]
> >[/color]
>
>[/color]

**Chung Leong** · Jul 17 '05, 03:59 AM

Re: to use or not to use a database for an archivable and searchable document

Based on what you've said, I would say no. It doesn't make sense to use a
database to do the job of a word-processor. Keep the Word file and use it to
generate a HTML version. Use Word's versioning mechanism or simply create a
new copy of the .doc file everytime you make changes.

Uzytkownik "Alexandre Plennevaux" <alexandre@la b-au.com> napisal w
wiadomosci news:4046003c$0 $13866$ba620e4c @news.skynet.be ...[color=blue]
> hello mates,
>
> my question is such: should i turn a 80 pages doc file into a database so
> that:
>
> - i can make it searchable through an online form
> - it can be modified and every modification archives the previous version,
> inside an "archive" table.
>
> ??
>
> The document could be described like this: it is a series of articles
> organised in 2 levels: sections and subsections.
> The user should be able to modify/erase/add articles , subsections and
> sections and still keep the original article inside an archive.
>
> The search system should cover both the current version and the archives.
>
> I get confused on how to organize the whole database system.
> I figured out that maybe it would be better to generate html files out of
> the database content (since it is not going to be changed everyday) and[/color]
then[color=blue]
> perform the search on these html files. Same for the archives. Every[/color]
updates[color=blue]
> generates a new set of html files containing the whole document.
>
> what do you think ?
>
> i need experimented advise here. please help !!
>
>[/color]

**Savut** · Jul 17 '05, 04:00 AM

Re: to use or not to use a database for an archivable and searchable document

He didn't said it's word format as I know

Savut

"Chung Leong" <chernyshevsky@ hotmail.com> wrote in message
news:feGdnY-_roasTtrdRVn-jQ@comcast.com. ..[color=blue]
> Based on what you've said, I would say no. It doesn't make sense to use a
> database to do the job of a word-processor. Keep the Word file and use it[/color]
to[color=blue]
> generate a HTML version. Use Word's versioning mechanism or simply create[/color]
a[color=blue]
> new copy of the .doc file everytime you make changes.
>
> Uzytkownik "Alexandre Plennevaux" <alexandre@la b-au.com> napisal w
> wiadomosci news:4046003c$0 $13866$ba620e4c @news.skynet.be ...[color=green]
> > hello mates,
> >
> > my question is such: should i turn a 80 pages doc file into a database[/color][/color]
so[color=blue][color=green]
> > that:
> >
> > - i can make it searchable through an online form
> > - it can be modified and every modification archives the previous[/color][/color]
version,[color=blue][color=green]
> > inside an "archive" table.
> >
> > ??
> >
> > The document could be described like this: it is a series of articles
> > organised in 2 levels: sections and subsections.
> > The user should be able to modify/erase/add articles , subsections and
> > sections and still keep the original article inside an archive.
> >
> > The search system should cover both the current version and the[/color][/color]
archives.[color=blue][color=green]
> >
> > I get confused on how to organize the whole database system.
> > I figured out that maybe it would be better to generate html files out[/color][/color]
of[color=blue][color=green]
> > the database content (since it is not going to be changed everyday) and[/color]
> then[color=green]
> > perform the search on these html files. Same for the archives. Every[/color]
> updates[color=green]
> > generates a new set of html files containing the whole document.
> >
> > what do you think ?
> >
> > i need experimented advise here. please help !!
> >
> >[/color]
>
>[/color]

to use or not to use a database for an archivable and searchable document

to use or not to use a database for an archivable and searchable document

Comment

Comment

Comment

Comment

Comment

Comment