[ | Date | | | 2011-11-11 19:00 -0500 | ] |
Somehow, I put myself in a situation where I have to use Access as front-end to a PostgreSQL database. Here are some of the SQL queries I see travelling over the network when refreshing forms:
SELECT "Id","TypeId","Name_","Description"
FROM "public"."ObjectData"
WHERE "Id" = 1036 OR "Id" = 1036 OR "Id" = 1036
OR "Id" = 1036 OR "Id" = 1036 OR "Id" = 1036
OR "Id" = 1036 OR "Id" = 1036 OR "Id" = 1036
OR "Id" = 1036.
And then:
SELECT "ItemId","TypeId"
FROM "public"."ItemData"
WHERE "ItemId" = 1036 OR "ItemId" = 1036 OR "ItemId" = 1036
OR "ItemId" = 1036 OR "ItemId" = 1036 OR "ItemId" = 1036
OR "ItemId" = 1036 OR "ItemId" = 1036 OR "ItemId" = 1036
OR "ItemId" = 1036.
Congratulations, Microsoft Access, on successfully avoiding redundant redundancies in your queries.
Quick links: