Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
The reason I've modelled the database like this, is to save space. I've created a utility which converts genealogical data from the Gedcom format to a MySQL-driven database. When dealing with genealogy it's fairly common to have individuals with more than one name; either you're not sure about the person's name, and want to refer to more than one names, or the person have a marriage name etc.

That name vs. lastname "bug" was a typo, and it doesn't affect the real problem here.

For simplicity, I could have had a name table looking like this:

person_id mediumint unsigned not null, /* references 'person' */ firstname varchar(255) not null, lastname varchar(255) not null

...but that's not really what I want. As I said, I want to save disk space, and by not duplicating data in the database I save a lot of space in this example.

However, after some reading I discovered Class::DBI::Join which seems to do what I'm after. The only problem is: I still can't get it to work. Any examples on using that class would have been great, as the example doesn't do it for me.

Thanks again!

In reply to Re: Re: Class::DBI and - possibly - complex data structures by Evil Attraction
in thread Class::DBI and - possibly - complex data structures by Evil Attraction

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (5)
As of 2024-03-28 23:04 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found