I think im good with a text for the db and search capability and the pdf for
pure display
jg
On Dec 15, 2012, at 5:31 PM, tamouse mailing lists
wrote:
> On Sat, Dec 15, 2012 at 11:22 AM, Jim Giner
> wrote:
>> On 12/15/2012 8:29 AM, tamouse mailing lists wrote:
>>>
>>> On Dec 13, 2012 4:50
On Sat, Dec 15, 2012 at 11:22 AM, Jim Giner
wrote:
> On 12/15/2012 8:29 AM, tamouse mailing lists wrote:
>>
>> On Dec 13, 2012 4:50 PM, "Jim Giner" wrote:
>>>
>>>
>>> Thanks for all the posts. After reading and googling all afternoon, I
>>
>> think the best approach for me is:
>>>
>>>
>>> Create
On Sat, Dec 15, 2012 at 11:21 AM, Jim Giner
wrote:
> On 12/15/2012 8:26 AM, tamouse mailing lists wrote:
>>
>> On Dec 13, 2012 4:50 PM, "Jim Giner" wrote:
>>>
>>>
>>> Thanks for all the posts. After reading and googling all afternoon, I
>>
>> think the best approach for me is:
>>>
>>>
>>> Create
On Sat, 2012-12-15 at 12:21 -0500, Jim Giner wrote:
> On 12/15/2012 8:26 AM, tamouse mailing lists wrote:
> > On Dec 13, 2012 4:50 PM, "Jim Giner" wrote:
> >>
> >> Thanks for all the posts. After reading and googling all afternoon, I
> > think the best approach for me is:
> >>
> >> Create two ma
On 12/15/2012 8:29 AM, tamouse mailing lists wrote:
On Dec 13, 2012 4:50 PM, "Jim Giner" wrote:
Thanks for all the posts. After reading and googling all afternoon, I
think the best approach for me is:
Create two macros in Word (done!) to export each of my .doc files to .txt
and .pdf forma
On 12/15/2012 8:26 AM, tamouse mailing lists wrote:
On Dec 13, 2012 4:50 PM, "Jim Giner" wrote:
Thanks for all the posts. After reading and googling all afternoon, I
think the best approach for me is:
Create two macros in Word (done!) to export each of my .doc files to .txt
and .pdf forma
On Dec 15, 2012 7:29 AM, "tamouse mailing lists"
wrote:
>
>
> On Dec 13, 2012 4:50 PM, "Jim Giner" wrote:
> >
> > Thanks for all the posts. After reading and googling all afternoon, I
think the best approach for me is:
> >
> > Create two macros in Word (done!) to export each of my .doc files to
On Dec 13, 2012 4:50 PM, "Jim Giner" wrote:
>
> Thanks for all the posts. After reading and googling all afternoon, I
think the best approach for me is:
>
> Create two macros in Word (done!) to export each of my .doc files to .txt
and .pdf formats.
>
> Create a sql table to hold the .txt contents
On Dec 13, 2012 4:50 PM, "Jim Giner" wrote:
>
> Thanks for all the posts. After reading and googling all afternoon, I
think the best approach for me is:
>
> Create two macros in Word (done!) to export each of my .doc files to .txt
and .pdf formats.
>
> Create a sql table to hold the .txt contents
On 12/13/2012 02:49 PM, Jim Giner wrote:
Thanks for all the posts. After reading and googling all afternoon, I
think the best approach for me is:
Create two macros in Word (done!) to export each of my .doc files to
.txt and .pdf formats.
Create a sql table to hold the .txt contents of my .doc f
Thanks for all the posts. After reading and googling all afternoon, I
think the best approach for me is:
Create two macros in Word (done!) to export each of my .doc files to
.txt and .pdf formats.
Create a sql table to hold the .txt contents of my .doc files, along
with a reference to the m
On 12/13/2012 2:40 PM, Bastien Koert wrote:
On Thu, Dec 13, 2012 at 12:41 PM, Matijn Woudt wrote:
On Thu, Dec 13, 2012 at 5:13 PM, Jim Giner wrote:
On 12/13/2012 10:56 AM, Bastien wrote:
Bastien Koert
On 2012-12-13, at 9:10 AM, Jim Giner
wrote:
Thanks for the input gentlemen. Two op
On Thu, Dec 13, 2012 at 12:41 PM, Matijn Woudt wrote:
> On Thu, Dec 13, 2012 at 5:13 PM, Jim Giner
> wrote:
>
>> On 12/13/2012 10:56 AM, Bastien wrote:
>>
>>>
>>>
>>> Bastien Koert
>>>
>>> On 2012-12-13, at 9:10 AM, Jim Giner
>>> wrote:
>>>
>>> Thanks for the input gentlemen. Two opposing view
On Thu, 2012-12-13 at 18:41 +0100, Matijn Woudt wrote:
> On Thu, Dec 13, 2012 at 5:13 PM, Jim Giner
> wrote:
>
> > On 12/13/2012 10:56 AM, Bastien wrote:
> >
> >>
> >>
> >> Bastien Koert
> >>
> >> On 2012-12-13, at 9:10 AM, Jim Giner
> >> wrote:
> >>
> >> Thanks for the input gentlemen. Two o
On Thu, Dec 13, 2012 at 5:13 PM, Jim Giner wrote:
> On 12/13/2012 10:56 AM, Bastien wrote:
>
>>
>>
>> Bastien Koert
>>
>> On 2012-12-13, at 9:10 AM, Jim Giner
>> wrote:
>>
>> Thanks for the input gentlemen. Two opposing viewpoints!
>>>
>>> I understand the concept of using files for the docs an
On 12/13/2012 10:56 AM, Bastien wrote:
Bastien Koert
On 2012-12-13, at 9:10 AM, Jim Giner wrote:
Thanks for the input gentlemen. Two opposing viewpoints!
I understand the concept of using files for the docs and a table to locate them
and id them. But I am of the opinion that modern dbs
Bastien Koert
On 2012-12-13, at 9:10 AM, Jim Giner wrote:
> Thanks for the input gentlemen. Two opposing viewpoints!
>
> I understand the concept of using files for the docs and a table to locate
> them and id them. But I am of the opinion that modern dbs are capable of
> handling very la
On Thu, Dec 13, 2012 at 3:32 PM, Jim Giner wrote:
> On 12/13/2012 9:19 AM, Matijn Woudt wrote:
>
>> On Thu, Dec 13, 2012 at 3:10 PM, Jim Giner
>> **wrote:
>>
>>
>>>
>>> I'm not sure if there's much difference between large text fields and
>> blobs, but I had a database (MySQL) with rows that had
On 12/13/2012 9:19 AM, Matijn Woudt wrote:
On Thu, Dec 13, 2012 at 3:10 PM, Jim Giner wrote:
I'm not sure if there's much difference between large text fields and
blobs, but I had a database (MySQL) with rows that had one blob each of
5-10 mb. At around 200-300 rows the database was pretty s
On Thu, Dec 13, 2012 at 3:10 PM, Jim Giner wrote:
> Thanks for the input gentlemen. Two opposing viewpoints!
>
> I understand the concept of using files for the docs and a table to locate
> them and id them. But I am of the opinion that modern dbs are capable of
> handling very large objects (of
Thanks for the input gentlemen. Two opposing viewpoints!
I understand the concept of using files for the docs and a table to
locate them and id them. But I am of the opinion that modern dbs are
capable of handling very large objects (of which these docs are NOT!)
much easier than years ago,
On 12-12-2012 21:40, Maciek Sokolewicz wrote:
On 12-12-2012 21:03, Paul M Foster wrote:
Second, you've hit on one of my pet peeves. Never never store huge
blocks of text in SQL files. It slows them down and there's no real
reason for it. There's no reason to force a DBMS to schlep around
massive
On 12-12-2012 21:03, Paul M Foster wrote:
Second, you've hit on one of my pet peeves. Never never store huge
blocks of text in SQL files. It slows them down and there's no real
reason for it. There's no reason to force a DBMS to schlep around
massive clumps of text or binary data. That's what dis
On Wed, Dec 12, 2012 at 01:00:41PM -0500, Jim Giner wrote:
> Slightly off-topic perhaps but I'm looking for general input here.
>
> New idea for a project - save the minutes of my firehouse meetings
> into a mysql table and build a ui to search them for words and such.
> The docs are written in W
24 matches
Mail list logo
