Re: [OT] XML in SQL (was: MySQL for Web Apps)
On 6 Feb 2004, at 02:37 pm, Chris Devers wrote: Anyway, it was pointed out to me in a different offlist response that I was probably answering the wrong question. Oh well -- it still seems like a useful (and under-publicized?) capability of the standard MySQL client, so maybe bringing it up will still be of use to someone... Very true .. I'm a PostGreSQLer rather than a MySQLer, and looking through the mailing lists there it looks like theres been talk of accessing the XML as data rather than as text ... h.. Feb 2003 .. I might poke some people! Rick Measham Senior Designer and Developer Printaform Pty Ltd Tel: (03) 9850 3255 Fax: (03) 9850 3277 http://www.printaform.com.au http://www.printsupply.com.au vcard: http://www.printaform.com.au/staff/rickm.vcf
Re: [OT] XML in SQL (was: MySQL for Web Apps)
On Fri, 6 Feb 2004, Rick Measham wrote: > On 6 Feb 2004, at 01:47 pm, Rick Measham wrote: > > Thanks Christ, > > erm .. sorry .. chris .. Heh... :) Anyway, it was pointed out to me in a different offlist response that I was probably answering the wrong question. Oh well -- it still seems like a useful (and under-publicized?) capability of the standard MySQL client, so maybe bringing it up will still be of use to someone... -- Chris Devers
Re: [OT] XML in SQL (was: MySQL for Web Apps)
On 6 Feb 2004, at 01:47 pm, Rick Measham wrote: Thanks Christ, erm .. sorry .. chris .. Rick Measham Senior Designer and Developer Printaform Pty Ltd Tel: (03) 9850 3255 Fax: (03) 9850 3277 http://www.printaform.com.au http://www.printsupply.com.au vcard: http://www.printaform.com.au/staff/rickm.vcf
Re: [OT] XML in SQL (was: MySQL for Web Apps)
On Wed, 4 Feb 2004, Rick Measham wrote: I'd love to see an XML parser embedded into SQL so that I can have: CREATE TABLE aTable (id serial, data XML); On 5 Feb 2004, at 05:21 pm, Chris Devers replied: Does this help? snip Is this along the lines of what you were hoping for? Thanks Christ, but not really at all. What I want is the ability to use XML as a data type so that I can have a field full of XML that is searchable. The output would be the'zactly the same as current output. The input would be XML as a string: > INSERT INTO data (id, user, data) VALUES (1, 'rick','RickMeasham'); > INSERT INTO data (id, user, data) VALUES (2, 'rick02','RickSmith'); # And then I could retrieve it: > SELECT * FROM data WHERE data:user:name='Rick' id | user | data --- 1 | rick | RickMeasham 2 | rick02 | RickSmith (2 rows returned) Cheers! Rick Measham Senior Designer and Developer Printaform Pty Ltd Tel: (03) 9850 3255 Fax: (03) 9850 3277 http://www.printaform.com.au http://www.printsupply.com.au vcard: http://www.printaform.com.au/staff/rickm.vcf
Re: XML::Parser isn't working on OX 10.3.2
On Feb 5, 2004, at 1:04 PM, Jack Herrington wrote: I believe the dev tools that we installed with Panther were the ones that came in the Panther installation disks. We installed XCode from a separate disk. I wasn't there, so I can't state with any certainty what you did or did not do. One thing is certain, though: If you don't have Xcode and GCC 3.3, you're not using the Panther dev tools. The OP indicated that he had upgraded his OS; he didn't say anything about also upgrading the dev tools until later. He spoke of Xcode as a new addition, implying that he'd had Project Builder before installing it. He also indicated that installing Xcode upgraded his GCC from 3.1 to 3.3. All of these things point to the fact that he had upgraded the OS to Panther, but continued to use Jaguar dev tools. Note that simply upgrading the OS does *not* automatically upgrade the dev tools. The dev tools (Xcode) disk is included with Panther, but it's a separate install. sherm--
RE: XML::Parser isn't working on OX 10.3.2
I agree, but I believe the dev tools that we installed with Panther were the ones that came in the Panther installation disks. We installed XCode from a separate disk. -Original Message- From: Sherm Pendley [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 4:50 AM To: Noah Hoffman Cc: 'Ken Williams '; ''[EMAIL PROTECTED]' '; Zalman Stern; Jack Herrington Subject: Re: XML::Parser isn't working on OX 10.3.2 On Feb 4, 2004, at 9:21 PM, Noah Hoffman wrote: > It appears the problem was with the version of gcc (the C > compiler). We > installed XCode which upgraded gcc from version 3.x to 3.3 The Xcode package also installs the correct headers and development libraries for Panther. That's far more likely to have made the difference than the switch from GCC 3.1 to 3.3. As a general rule, each release of Mac OS X has its own set of development tools, and dev tools intended for earlier or later releases don't work very well if at all. sherm--
Re: MacPerl INC question
In a message dated 2/5/04 12:37:24 AM, [EMAIL PROTECTED] writes:
>
> > So my next question is: What is Acrobat doing when opening a file that
> > SetFileInfo isn't?
>
> Setting the correct file type? :^)
>
> According to your previous message, you're doing this:
>
> MacPerl::SetFileInfo('CARO', 'PDF', $path);
>
> HFS file and creator types are four-bytes long; the file type for
> PDF is "PDF ", with a trailing space, not "PDF". So try changing the
> above line to:
>
> MacPerl::SetFileInfo('CARO', 'PDF ', $path);
>
> and I think you'll be set.
>
>
Right you are. Thanks for reminding me that it's the small things in life
that matter... and it's a spaceband.
-Alan
Re: XML::Parser isn't working on OX 10.3.2
On Feb 4, 2004, at 9:21 PM, Noah Hoffman wrote: It appears the problem was with the version of gcc (the C compiler). We installed XCode which upgraded gcc from version 3.x to 3.3 The Xcode package also installs the correct headers and development libraries for Panther. That's far more likely to have made the difference than the switch from GCC 3.1 to 3.3. As a general rule, each release of Mac OS X has its own set of development tools, and dev tools intended for earlier or later releases don't work very well if at all. sherm--
RE: XML::Parser isn't working on OX 10.3.2
Hi Ken, It appears the problem was with the version of gcc (the C compiler). We installed XCode which upgraded gcc from version 3.x to 3.3, now XML::Parser installs and works fine. -Noah -Original Message- From: Ken Williams To: Noah Hoffman Cc: '[EMAIL PROTECTED]'; Jack Herrington; Zalman Stern Sent: 2/4/2004 5:48 AM Subject: Re: XML::Parser isn't working on OX 10.3.2 On Tuesday, February 3, 2004, at 05:02 PM, Noah Hoffman wrote: > Hello, > > I've just upgraded our build machines from 10.2.8 to 10.3.2 and > now all > of my perl scripts are broken. It seems XML::Parser is the culprit, > I'm > gettting an error of: > > "Can't load '/usr/local/lib/libExpant.dylib' formodule > XML::Parser::Expat: /usr/local/lib/libexpat.dylib(2): Not a > recognisable > object file at /Library/Perl/XML/Parser.pm line 14" libExpant, really? Former pant? > > I've tried reinstalling the Parser module with no luck. Does anyone > have > any ideas here? What does "no luck" mean? Did XML::Parser fail its tests, or did it pass and install correctly but still not solve the problem? -Ken
Re: Installing DBD::mysql
Thanks, that helped. I promise to check the archives thoroughly in the future. The make test still stuck on PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00base...ok t/10dsnlist but the make install went by without problems. - Jan Mike Schienle wrote: > >On Feb 04, 2004, at 01:13 PM, Jan Eden wrote: > >> Thanks, I read your post carefully. MySQL and the Perl DBI module are >> installed. >> >> I am still stuck, though. The command perl Makefile.PL for DBD::mysql >> tells me my setting looks good and uses mysql_config to determine >> various flags. >> >> make / make test give me an error: > >That's in the archives at >http://www.mail-archive.com/[EMAIL PROTECTED]/msg05738.html > >Mike Schienle, Custom Visuals, LLC >http://www.customvisuals.com/ > -- The day Microsoft makes something that doesn't suck is the day they start selling vacuum cleaners.
Re: MacPerl INC question
At 10:48 pm -0500 4/2/04, [EMAIL PROTECTED] wrote:
Interestingly, the problem I was trying to solve with MacPerl's
SetFileInfo is still open. Once Perl set the creator/type...
At 6:23 pm -0500 3/2/04, [EMAIL PROTECTED] wrote:
MacPerl::SetFileInfo('CARO', 'PDF', $path);
Is that precisely what you are writing? If so then you need 4 bytes
in the file type and I guess it should be 'PDF '
JD
