Re: Limit to Field Length in DB

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 16741
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? They save it as plain txt in msword with dos line breaks.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.)
and

not required, try wrapping in in the [pre]tag[/pre] as a test to see if that might help. We don't embed html inside our docs. Never tried to even let these people do this. Reference to other html docs are handled out of the data base not inside the doc. Now that is the way we do it. Doesn't mean it is right for you. > >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.)All our tech docs are on our private area of your servers so the search engine part is not a issue for us. The public can not get to them. But I assume the would pick up the text using the [include] tag >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? > >MarkNo not really. You biggest problem is getting a large story into a place to edit online. Maybe siteedit pro might be away to go to do the editing of the [included] file...Jay, John, Grant, somebody else want to chime in on using siteedit to write the story part and then include it into an html doc via [writefile]=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com =============================================== 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? They save it as plain txt in msword with dos line breaks.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.)
and

not required, try wrapping in in the [pre]tag[/pre] as a test to see if that might help. We don't embed html inside our docs. Never tried to even let these people do this. Reference to other html docs are handled out of the data base not inside the doc. Now that is the way we do it. Doesn't mean it is right for you. > >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.)All our tech docs are on our private area of your servers so the search engine part is not a issue for us. The public can not get to them. But I assume the would pick up the text using the [include] tag >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? > >MarkNo not really. You biggest problem is getting a large story into a place to edit online. Maybe siteedit pro might be away to go to do the editing of the [included] file...Jay, John, Grant, somebody else want to chime in on using siteedit to write the story part and then include it into an html doc via [writefile]=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com =============================================== grichter@panavise.com (Gary Richter)

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:

How to get shownext to just shownext once (1997) Help! WebCat2 bug (1997) WebCommerce: Folder organization ? (1997) [include ...] behavior (1997) Templates on Unix & CGI on Mac? (1997) Adding Header Values with [SetHeader] (1998) Multiple prices (1997) 2.1 Stuff (1998) nested context (1998) I can help! (1996) pictures / referrer etc. (1998) Sku numbers (1997) [WebDNA] Amazon EC2 (2009) Problems with webcat 2.01 for NT (1997) [date] for today's date, while inside old order file (1998) authenticating a second user (1997) OK, here goes... (1997) Add more fields to an existent data base (1997) Resume Catalog ? (1997) protect tag on NT (1997)