On Jan 17, 2007, at 2:08 AM, Neal Clark wrote:
> the stuff table is huge. the actual requirements are "infinite rows
> spanning an infinite amount of disk space," but i'm working with my
then stuff like this:
> accounts INTEGER[]
> id SERIAL PRIMARY KEY
should be (in postgres):
> accounts BIGINT
> id BIGSERIAL PRIMARY KEY
overall though, i don't understand why you're not using a lookup
table and normalizing your db:
stuff
id BIGSERIAL
data TEXT
date_added TIMESTAMP
account
id BIGSERIAL PRIMARY KEY
name VARCHAR,
email BLAH
regex BLAH
stuff_2_account
id_stuff BIGINT references stuff(id)
id_account BIGINT references account(id)
date_related TIMESTAMP
relation_info TEXT blah blah
then you just use the lookup table to map the classes
RoseDB handles this VERY easily via the ManyToMany relationship
http://search.cpan.org/~jsiracusa/Rose-DB-Object/lib/Rose/DB/Object/
Metadata/Relationship/ManyToMany.pm
// Jonathan Vanasco
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
