Re: FEA REQ: One .hdr, multiple .db's

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 52377
interpreted = N
texte = At 2:00 AM -0700 8/21/03, John Peacock wrote: >Scott Anderson wrote: >> That sounds like it could be useful. Although it might get confusing, after >> a while, remembering which hdr files belong to which databases, when viewing >> web-site contents. Any other opinions out there with regard to this feature >> request? > >I personally don't see much use from the feature. If I were in the >situation, I would use the .hdr file as a template; copy it to a new >temporary .db file then append the records. The whole point of >using the .hdr and .db files seperate was to be able to append new >fields and refresh and have the table automatically grow wider. >.hdr files are of limited functionality (since you cannot insert new >fields in the middle) to begin with. > >I don't see a lot of advantage to have to specify >[...&hdr=^header.hdr...] on every single call that database (and you >know you will forget it once) when you can easily embed the headers >in the actual database before appending records. I'm with John. People love their .hdr files, but I prefer to have all-in-one db files. I do exactly as John suggests, and use essentially a header file as a template when necessary, then populate the new database. Couldn't be simpler, and fewer files to keep track of on the server too. Since I sit next to my server, I do a lot of checking of the live databases as I develop, and it's handy to see the headers in the same file, particularly when there's been a time lapse between development sessions. Terry ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: FEA REQ: One .hdr, multiple .db's ( "WebDna @" 2003)
  2. Re: FEA REQ: One .hdr, multiple .db's ( Terry Wilson 2003)
  3. Re: FEA REQ: One .hdr, multiple .db's ( Kenneth Grome 2003)
  4. Re: FEA REQ: One .hdr, multiple .db's ( Matthew Bohne 2003)
  5. Re: FEA REQ: One .hdr, multiple .db's ( "Gary Krockover" 2003)
  6. Re: FEA REQ: One .hdr, multiple .db's ( Kenneth Grome 2003)
  7. Re: FEA REQ: One .hdr, multiple .db's ( "Nitai @ ComputerOil" 2003)
  8. Re: FEA REQ: One .hdr, multiple .db's ( Kenneth Grome 2003)
  9. Re: FEA REQ: One .hdr, multiple .db's ( "Nitai @ ComputerOil" 2003)
  10. Re: FEA REQ: One .hdr, multiple .db's ( Matthew Bohne 2003)
  11. Re: FEA REQ: One .hdr, multiple .db's ( Terry Wilson 2003)
  12. Re: FEA REQ: One .hdr, multiple .db's ( "Nitai @ ComputerOil" 2003)
  13. Re: FEA REQ: One .hdr, multiple .db's ( Kenneth Grome 2003)
  14. Re: FEA REQ: One .hdr, multiple .db's ( "Scott Anderson" 2003)
  15. Re: FEA REQ: One .hdr, multiple .db's ( "Scott Anderson" 2003)
  16. Re: FEA REQ: One .hdr, multiple .db's ( Stuart Tremain 2003)
  17. Re: FEA REQ: One .hdr, multiple .db's ( Donovan 2003)
  18. Re: FEA REQ: One .hdr, multiple .db's ( Scott Anderson 2003)
  19. Re: FEA REQ: One .hdr, multiple .db's ( Matthew Bohne 2003)
  20. Re: FEA REQ: One .hdr, multiple .db's ( Brian Fries 2003)
  21. Re: FEA REQ: One .hdr, multiple .db's ( John Hill 2003)
  22. Re: FEA REQ: One .hdr, multiple .db's ( John Peacock 2003)
  23. Re: FEA REQ: One .hdr, multiple .db's ( "Scott Anderson" 2003)
  24. Re: FEA REQ: One .hdr, multiple .db's ( "Nitai @ ComputerOil" 2003)
  25. Re: FEA REQ: One .hdr, multiple .db's ( Donovan 2003)
  26. Re: FEA REQ: One .hdr, multiple .db's ( "Nitai @ ComputerOil" 2003)
  27. Re: FEA REQ: One .hdr, multiple .db's ( "WebDna @" 2003)
  28. Re: FEA REQ: One .hdr, multiple .db's ( "Nitai @ ComputerOil" 2003)
  29. FEA REQ: One .hdr, multiple .db's ( Matthew Bohne 2003)
At 2:00 AM -0700 8/21/03, John Peacock wrote: >Scott Anderson wrote: >> That sounds like it could be useful. Although it might get confusing, after >> a while, remembering which hdr files belong to which databases, when viewing >> web-site contents. Any other opinions out there with regard to this feature >> request? > >I personally don't see much use from the feature. If I were in the >situation, I would use the .hdr file as a template; copy it to a new >temporary .db file then append the records. The whole point of >using the .hdr and .db files seperate was to be able to append new >fields and refresh and have the table automatically grow wider. >.hdr files are of limited functionality (since you cannot insert new >fields in the middle) to begin with. > >I don't see a lot of advantage to have to specify >[...&hdr=^header.hdr...] on every single call that database (and you >know you will forget it once) when you can easily embed the headers >in the actual database before appending records. I'm with John. People love their .hdr files, but I prefer to have all-in-one db files. I do exactly as John suggests, and use essentially a header file as a template when necessary, then populate the new database. Couldn't be simpler, and fewer files to keep track of on the server too. Since I sit next to my server, I do a lot of checking of the live databases as I develop, and it's handy to see the headers in the same file, particularly when there's been a time lapse between development sessions. Terry ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Terry Wilson

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:

Date search - yes or no (1997) Hello??? (1997) Missing something simple?? (1998) sharing cookie recepies (1998) [if] and [showif] (2002) pc (1997) Word search (1997) WC1.6 to WC2 date formatting (1997) Great product and great job ! (1997) Mac Programs (1998) Whats up with emailer? (1998) Re:ListFields and [name] (1997) Extended [ConvertChars] (1997) Problems with [Applescript] (1997) Browser Problem?!? Still getting Error message using (1997) Non WebDNA forms and timed popups... (2002) [OT] Argh... (2004) The EMailer and the Blank menu bar? (1999) Denying access by IP address (2000) Sendmail on OSX/Communigate Pro (2002)