473,387 Members | 1,536 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,387 software developers and data experts.

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

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 then
perform the search on these html files. Same for the archives. Every updates
generates a new set of html files containing the whole document.

what do you think ?

i need experimented advise here. please help !!
Jul 17 '05 #1
6 1691
Alexandre Plennevaux wrote:
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.


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

Jul 17 '05 #2
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" <al*******@lab-au.com> wrote in message
news:40***********************@news.skynet.be...
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 then perform the search on these html files. Same for the archives. Every updates generates a new set of html files containing the whole document.

what do you think ?

i need experimented advise here. please help !!


Jul 17 '05 #3
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" <we***@hotmail.com> wrote in message
news:6R********************@news20.bellglobal.com. ..
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" <al*******@lab-au.com> wrote in message
news:40***********************@news.skynet.be...
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

then
perform the search on these html files. Same for the archives. Every

updates
generates a new set of html files containing the whole document.

what do you think ?

i need experimented advise here. please help !!

Jul 17 '05 #4
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" <al*******@lab-au.com> wrote in message
news:40*********************@news.skynet.be...
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" <we***@hotmail.com> wrote in message
news:6R********************@news20.bellglobal.com. ..
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" <al*******@lab-au.com> wrote in message
news:40***********************@news.skynet.be...
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 then
perform the search on these html files. Same for the archives. Every

updates
generates a new set of html files containing the whole document.

what do you think ?

i need experimented advise here. please help !!



Jul 17 '05 #5
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" <al*******@lab-au.com> napisal w
wiadomosci news:40***********************@news.skynet.be...
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 then perform the search on these html files. Same for the archives. Every updates generates a new set of html files containing the whole document.

what do you think ?

i need experimented advise here. please help !!

Jul 17 '05 #6
He didn't said it's word format as I know

Savut

"Chung Leong" <ch***********@hotmail.com> wrote in message
news:fe********************@comcast.com...
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" <al*******@lab-au.com> napisal w
wiadomosci news:40***********************@news.skynet.be...
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

then
perform the search on these html files. Same for the archives. Every

updates
generates a new set of html files containing the whole document.

what do you think ?

i need experimented advise here. please help !!



Jul 17 '05 #7

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
by: Yasso Picasso | last post by:
Greetings, I have to admit that I'm still a beginner in the database field, but I'm actively studying, and this is why I will be utterly grateful for the proper, accurate, and wise guidance to...
0
by: Yasso | last post by:
Greetings, I have to admit that I'm still a beginner in the database field, but I'm actively studying, and this is why I will be utterly grateful for the proper, accurate, and wise guidance to...
5
by: PR | last post by:
Searchable product images + prices database? What system should I use to put a database on the WEB which shows images and allows searches, including searches within given price ranges for...
3
by: sandrina | last post by:
Hello everyone, My name is Debi and I am an Administrative assistant with a large company in their sourcing department. I was hired one month ago, and walked in to a HUGE filing nightmare. My...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: ryjfgjl | last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
0
by: emmanuelkatto | last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud. Please let me know. Thanks! Emmanuel
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
1
by: Sonnysonu | last post by:
This is the data of csv file 1 2 3 1 2 3 1 2 3 1 2 3 2 3 2 3 3 the lengths should be different i have to store the data by column-wise with in the specific length. suppose the i have to...
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
0
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
0
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.