John and Svilen, thank you very much for your quick, informative replies. Looks like I have my work cut out for me!
--- John Siracusa <[EMAIL PROTECTED]> wrote: > On 1/11/06 9:16 AM, Scott Karns wrote: > > ... > > and the second is a 'time' column type used to > > store class (as in school) scheduling > > information. [...] After looking through some > > of the RDBO::Metadata space, I believe my best > > bet is to create a new scalar column class that > > will convert the Pg data to an integer upon > > access and back to the Pg form upon store as > > well as some ability to play well with > > timestamp objects. > > I had Pg time types in a few early versions of RDBO, > but I could never decide on a nice client-side > representation. An integer seems like a strange > choice to me. ... John, I guess my embedded systems background is showing -- I was thinking in terms of the low-level, internal representation of time being an unsigned integer modulo 24 hours to whatever resolution rather than the client view of a time object, its attributes and behavior. While I've been writing code for longer than I care to state, the perl OO paradigm is newer territory for me. ;) Thanks again, I'm sure I'll be back. Scott __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
