Marnen Laibow-Koser wrote:

> Question: why do you need to duplicate the filesystem's directory
> information in the DB?

The filesystem's directory information has medical reports in Word 
document format.
The naming convention is:
"last name, first name{, middle initial, title}, date of study, 
procedure"

I use 'antiword' to parse the document and get the information I want 
(win32OLE is way, way, WAY too slow).

The proofreaders need to know the date of study and how long the exam's 
been in the directory - which can't easily be determined from just 
looking at the directory (it's awkward).

My first version of the page literally just built the table with the 
information to be displayed on-the-fly, every time it was refreshed. I 
figured this may be an issue if too many people attempted to do it at 
once, so I stuck it in the database instead - now the background job 
does the checking of the directory and the parsing of the files.

Additionally, I'm in fact checking a couple of directories and offering 
them as options in a menu in my view, again, to make their life easier

--------
Of course, and this is the issue which brings me here in the first 
place, when I click on one of those options after a couple of sweeps 
happened, the rails log overflows with that kind of lines:

 [4;35;1mReport Load (0.0ms) [0m    [0mSELECT * FROM "reports" WHERE 
("reports"."filename" = 'SomeReportName.doc') LIMIT 1 [0m
   [4;36;1mReport Update (0.0ms) [0m    [0;1mUPDATE "reports" SET 
"updated_at" = '2009-08-19 13:51:22', "absolute_age" = 31393 WHERE "id" 
= 927 [0m

Which is what bothered me and what bothers you :)
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to