> I think what you want is not really going to fit. The nature of > DISTINCT doesn't really map to whole entities - which one should it > return when several are not 'distinct'? If it picks some arbitrarily, > then the values you get back in the other columns aren't going to be > deterministic and probably aren't much use to you. > > With that in mind, I don't see any problem with the original snippet > you posted.
Well, so far, Elixir, SQLAlchemy and SQLObjects have all made "easy things hard" and "harder things impossible". In my usage, I'm failing to see the advantage of these over: import pgdb x = pgdb.connect ... othe than that's not the way TurboGears seems to be geared. My SQL needs are fairly modest, and my SQL knowledge even more so. The snippet I posted returns a list of tuples, which I could do more easily with pgdb. I figured if I was going to all the trouble of making some sort of mapping of python variable names to SQL columns, it might be nice to be able to use them. ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
