x/y/z as an identifier, as you suggest, is also an option
>> with it's own benefits and downsides; nothing prevents you from taking any
>> or all of those approaches at the same time.
>>
>>
>> - Original Message -
>> > From: "Larry Martell
self joins on large tables. I think I will end up going with using
x/y/z.
>
> - Original Message -
> > From: "Larry Martell"
> > To: "Steven Siebert"
> > Cc: "mysql mailing list"
> > Sent: Friday, 22 November, 2013 3:17:44 PM
&g
#x27;s own benefits and downsides; nothing prevents you from taking any
> or all of those approaches at the same time.
>
>
> - Original Message -----
> > From: "Larry Martell"
> > To: "Steven Siebert"
> > Cc: "mysql mailing list"
>
ng any or all of
those approaches at the same time.
- Original Message -
> From: "Larry Martell"
> To: "Steven Siebert"
> Cc: "mysql mailing list"
> Sent: Friday, 22 November, 2013 3:17:44 PM
> Subject: Re: XML to RDB
>
> Yes, I will need to
On Fri, Nov 22, 2013 at 8:05 AM, Steven Siebert wrote:
> Hi Larry,
>
> I'm trying to figure out what your wanting to do with the data once its in
> mysql? At first it seemed you didn't want to put it in as a lob because
> you might want to query on the data in different ways (kind of an
> assump
Hi Larry,
I'm trying to figure out what your wanting to do with the data once its in
mysql? At first it seemed you didn't want to put it in as a lob because
you might want to query on the data in different ways (kind of an
assumption on my part, but a common reason to do this). Then, you thought
I have a need to store data that comes in an XML file in MySQL. I don't
want to store the entire file as a CBLOB, and it doesn't lend itself to
loading with Load XML. I am looking for tools that will help me create the
schema and parse and load the data. I have googled for this and I've found
many
