Re: Limit to Field Length in DB

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 16739
interpreted = N
texte = At 11:26 AM 3/25/98 -0800, you wrote: >Our engineering dept writes long tech articles, and what we did is have >them ftp them into a folder. Lets say tech1.txt and tech2.txt is the names >of the files they uploaded via ftp. The they fill out a form that lists >the date, writer, subject, file name and a bunch of other search words and >so forth. Then when somebody searches for an article on the display >template right after the header we have something close to this > >[include /tech/[filename]] > >where the [filename] comes from the searchable data base. > >I know this is not do what you want to do. But it is a sloution that works. >I have been thinking about using the [include story.txt] method also. My question is, how do you handle the formating of the text that the [include] statement refers to? In particular, do the engineers add

or
tags within their document for the correct paragraph spacing? How about links to other documents? I have tips next to the HTML form that tells the editor about HTML tags they might need to include in the article text (like: for a paragraph return put in a

tag.) My idea was for the editor to input a story into an web form and then the story would be flowed into our template that formats their story and the page. I then use a [writefile] to create the html page. My thinking is that stories would be entered into the story.db, they would reside there for the editor to work on. Once the story is final, they would publish it to the web site using [writefile] (The reason for the actual html page was for search engine spiders as discussed in many previous posts.)After the story has been published, the record from story.db would be removed (or maybe not). The published story info (Title, Author, Keywords, Filename) would then be placed into another database that would allow end-user searching.Am I making this more complicated that it needs to be?Mark -------------------------------------------------------------------- Mark Anderson There's nothing to fear ... Don't be afraid, marka@fabian.com To let the freaky freaky into your brain. -- DJ Keoki Work: http://www.fabian.com/ Home: http://members.home.com/manderson1/ -------------------------------------------------------------------- Associated Messages, from the most recent to the oldest:

    
  1. Re: Limit to Field Length in DB (PCS Technical Support 1998)
  2. Re: Limit to Field Length in DB (Mark Anderson 1998)
  3. Re: Limit to Field Length in DB (grichter@panavise.com (Gary Richter) 1998)
  4. Re: Limit to Field Length in DB (Mark Anderson 1998)
  5. Re: Limit to Field Length in DB (grichter@panavise.com (Gary Richter) 1998)
  6. Re: Limit to Field Length in DB (PCS Technical Support 1998)
  7. Limit to Field Length in DB (Mark Anderson 1998)
At 11:26 AM 3/25/98 -0800, you wrote: >Our engineering dept writes long tech articles, and what we did is have >them ftp them into a folder. Lets say tech1.txt and tech2.txt is the names >of the files they uploaded via ftp. The they fill out a form that lists >the date, writer, subject, file name and a bunch of other search words and >so forth. Then when somebody searches for an article on the display >template right after the header we have something close to this > >[include /tech/[filename]] > >where the [filename] comes from the searchable data base. > >I know this is not do what you want to do. But it is a sloution that works. >I have been thinking about using the [include story.txt] method also. My question is, how do you handle the formating of the text that the [include] statement refers to? In particular, do the engineers add

or
tags within their document for the correct paragraph spacing? How about links to other documents? I have tips next to the HTML form that tells the editor about HTML tags they might need to include in the article text (like: for a paragraph return put in a

tag.) My idea was for the editor to input a story into an web form and then the story would be flowed into our template that formats their story and the page. I then use a [writefile] to create the html page. My thinking is that stories would be entered into the story.db, they would reside there for the editor to work on. Once the story is final, they would publish it to the web site using [writefile] (The reason for the actual html page was for search engine spiders as discussed in many previous posts.)After the story has been published, the record from story.db would be removed (or maybe not). The published story info (Title, Author, Keywords, Filename) would then be placed into another database that would allow end-user searching.Am I making this more complicated that it needs to be?Mark -------------------------------------------------------------------- Mark Anderson There's nothing to fear ... Don't be afraid, marka@fabian.com To let the freaky freaky into your brain. -- DJ Keoki Work: http://www.fabian.com/ Home: http://members.home.com/manderson1/ -------------------------------------------------------------------- Mark Anderson

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

corrupted jpgs (2003) I am dumb. No see [variable] (2003) Multiple security dbs (1997) [OT] SQL and Crackers (2000) numfound question (2005) Email notification to one of multiple vendors ? (1997) Unexpected error (1997) WebDNA to Apache RewriteMap (2005) Re:Emailer and encryption (1997) ShipToState question (1998) Finding max value for a field (1997) Only charge card when product shipped ? (1997) Possible Bug in 2.0b15.acgi (1997) Search/sort in URL Was: GuestBook example (1997) FAX orders (1996) Special delete ... (1997) A question on sub-categories (1997) Overridding E-Mailer (1998) Tab Charactor (1997) Serial Number Question (1997)