comment on

I'm now writing a simple module. This module represents one object. I need the ablitily to store the state of this object in the database and to restore it from the database.

To sole this task I want to add 2 methods to the object:

serialize() — it will return scalar with some string that represents the object state
spawn() — this is a constractor, it recieves the scalar that I got from serialize() method and will create the object

I'm planning to use YAML to serialize some object internals that are needed to recreate the object, and I'm going to save in the serialized string some number to make it possible to chagne serialazation format, but to store the compatibility.

What do you think? Is this aproach good, or should I do something else to solve my task of storing object in the databse.

UPDATE: I've created and released module Time::ETA that does the exact serialization that I have described in this post.

In reply to Best way to store object in db by bessarabov

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.


laziness, impatience, and hubris
	PerlMonks