On Tue, Jun 19, 2007 at 02:21:51AM +0300, [EMAIL PROTECTED] wrote: > > Perfectly. Although all the hassle makes me think even harder if > > there is really no other way of connecting these two database > > tables. A casted join with string comparison gets dirtier every > > time I look at it. :( > > excuse me if it sounds dumb... what about a middleman table of proper > (casted) values that is automaticaly build by some trigger? > i can guess at least 3 objections right now, but it is an option in > general principle...
Doesn't sound dumb at all. I assume you are thinking of an intermediary table that is connecting primary keys like "row 10 of dns table is connected to row 515 of dhcp table". Yes, I'm considering that, too. With "secondary" properties SQLAlchemy makes such many-to-many relations really easy. However I have a higher risk of rows that have different IP address values in this case. I'll think about it though. Thanks for the suggestion. Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
