Hi Mat, 3) actually this one was caused by my solution for 2) not being fully debugged on my side, working OK now.
In fact as far as I'm concerned all the issues I've addressed in my OP have been circumvented by yours truly so the issue can be closed, but the bitter taste left by the experience will take a while to fade away. Cheers, Deny On Wednesday, May 26, 2021 at 10:53:40 AM UTC-3 Mat wrote: > Hi Deny, > > I feel you. > > 2) I opened an issue > <https://github.com/googleads/google-ads-python/issues/434> regarding > this point a few days ago. There is an answer from the Python library > maintainers too, that works for me. > > 3) I did not run into this issue yet. At least I hope so (would be very > bad). Could you provide an example? > > 4) This is not limited to fields named "type". Technically, this could > affect many other field-names > <https://developers.google.com/google-ads/api/docs/client-libs/python/library-version-10#field_names_that_are_reserved_words> > > too. > But there is hope: "# We make SOME exceptions for certain names that > collide with builtins." > <https://github.com/googleapis/gapic-generator-python/blob/master/gapic/utils/reserved_names.py> > ^^ > > Regards > Mat > > deny.w...@wmccann.com schrieb am Dienstag, 25. Mai 2021 um 18:47:22 UTC+2: > >> 1) google_ads changed to googleads in class path: REALLY guys, you >> couldn't live with an old name, you had to go ahead and BREAK THINGS for >> users? If we are so irrelevant, why bother developing stuff and releasing >> it publicly? >> >> 2) To whom it may concern, MessageToJson and MessageToDict from >> google.protobuf.json_format no longer work. I've created a workaround, but >> really who cares? >> >> 3) When issuing search_stream and querying ad_group, ad_group_ad, etc., >> "where campaign.id = xxxxx" no longer works, bringing no results. The >> reason I was using this was so I could implement some sort of incremental >> query based on campaign age and status, otherwise we get a HUGE amount of >> data in the results (I'm responsible for Coca-Cola, General Motors, Nestle >> and some other large accounts in Brazil). Now we have to go back to >> filtering by client which is in practice no filter at all, and by doing >> that we'll clog your servers, congratulations. >> >> 4) Things keep getting better and better as any column named "type" NEEDS >> TO BE QUERIED with the original name, but HAS TO BE READ as "type_". >> >> If I sound pissed is because I AM. At this point, all things being equal, >> I'm recommending ANYTHING but google to my clients. Your devs are >> unbelievably incompetent, and I would bet good money they think they're >> incredible (Dunning-Kruger anyone?). Complexity is not a measure of >> success, quite the opposite in fact. Your code is HORRIBLE and an >> embarrassment to Google. >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/727b13c8-ab2f-4da0-ba76-78485a5a8916n%40googlegroups.com.
