Thread: Was my question inappropriate for postgres?
I would like to know if psqlodbc_13_02 is compatible with M365.
Also, could you please tell me which of the psqlodbc_13_02 would be
suitable to Windows 10 64-bit?
On 7/24/22 16:56, Taka Taka wrote: > Hello. > > I posted question bellow. > > Hello. > I would like to know if psqlodbc_13_02 is compatible with M365. > Also, could you please tell me which of the psqlodbc_13_02 would be > suitable to Windows 10 64-bit? > > Was my question inappropriate? It was appropriate. It is just that Windows users are not all that common on this list, especially that subset that are using ODBC. You might have better luck subscribing to and asking question on the Postgres ODBC list: https://www.postgresql.org/list/pgsql-odbc/ > I wanted to know if the pdbc driver above would be compatible to > Microsoft's M365. > Also, I find variety in the odbc driver. > Is it possible to know which of the driver is suitable to Windows 10 64-bit? I would say from here: https://www.postgresql.org/ftp/odbc/versions/msi/ psqlodbc_13_02_0000-x64.zip psqlodbc_13_02_0000-x64.zip Try it and see, if you don't want to wait for response from this list or the ODBC list. > Or could you please tell me where to inquire? > -- Adrian Klaver adrian.klaver@aklaver.com
On 25/07/22 11:56, Taka Taka wrote: > Hello. > > I posted question bellow. > > Hello. > I would like to know if psqlodbc_13_02 is compatible with M365. > Also, could you please tell me which of the psqlodbc_13_02 would be > suitable to Windows 10 64-bit? > Was my question inappropriate? > I wanted to know if the pdbc driver above would be compatible to > Microsoft's M365. > Also, I find variety in the odbc driver. > Is it possible to know which of the driver is suitable to Windows 10 > 64-bit? > Or could you please tell me where to inquire? > Hi, Please do not top post, bottom post like me. I suspect that most people do not know what 'M365' is, would be good to explain. Am curious as to what 'M365' is! Can't help with Microsoft stuff, as I mainly use Linux, though I've been forced to use Microsoft O/S's in the past (last time was in a VM on Linux a few years back). If you are using Postgres for really large data volumes, and/or require high performance, you might be better to upgrade to Linux --- it really depends on your own specific situation. Note that most servers run Linux! Cheers, Gavin
On 7/24/22 17:15, Gavin Flower wrote: > On 25/07/22 11:56, Taka Taka wrote: >> Hello. > I suspect that most people do not know what 'M365' is, would be good to > explain. Am curious as to what 'M365' is! New branding and pricing(subscription) of MS Office. Microsoft 365 https://www.microsoft.com/en-us/microsoft-365 > > Cheers, > Gavin > > > -- Adrian Klaver adrian.klaver@aklaver.com
Hello.I posted question bellow.
And? No takers? I wonder why. Maybe the question is unclear? This is really surprising :)
Hello.
I would like to know if psqlodbc_13_02 is compatible with M365.
Also, could you please tell me which of the psqlodbc_13_02 would be
suitable to Windows 10 64-bit?
What is M365? Is it a part of Microsoft Office 365, aka "O365"? Is it related to M-16? What di you mean by "driver suitable for Windows 10"? If the driver can be installed and configured by the MS ODBC driver administrator, then I guess it's suitable. Make sure the driver you use is mauve, they take the least RAM
What part of Office 365 do you want the compatibility with? Excel?Was my question inappropriate?I wanted to know if the pdbc driver above would be compatible to Microsoft's M365.
Also, I find variety in the odbc driver.
I don't. ODBC drivers implement the same protocol when communicating with the database and they all work the same. Here is what I have:
[mgogala@umajor ~]$ rpm -qa *odbc*
oracle-instantclient-odbc-21.5.0.0.0-1.x86_64
postgresql-odbc-13.01.0000-2.fc36.x86_64
msodbcsql17-17.10.1.1-1.x86_64
[mgogala@umajor ~]$
The string "f36" in the PostgreSQL ODBC package name denotes a very special version of Windows, more advanced than even Windows 11. I was able to connect all 3 of the drivers above to LibreOffice and use them to query the underlying database. I was able to do the same on my Windows 8.1, with all 3 of those drivers.
Is it possible to know which of the driver is suitable to Windows 10 64-bit?
Suitable how? What exactly do you want to do? What does the word "suitable" even mean in the context you're using it?
Or could you please tell me where to inquire?
There is this site named "https://www.google.com" which can be used to find a lot of useful information and some paid ads, too. As of lately, I prefer DDG, but that's just a personal preference.
If there were no takers for the first question, that may say something about the question. At this point, you gotta ask yourself one question only: do I feel lucky?
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com
I suspect that most people do not know what 'M365' is, would be good to explain. Am curious as to what 'M365' is!
M365 is the latest member in the ArmaLite M-16 family of products. It can be connected to database to track down the DBA who don't check their backups.
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com
On 25/07/22 12:19, Adrian Klaver wrote: > On 7/24/22 17:15, Gavin Flower wrote: >> On 25/07/22 11:56, Taka Taka wrote: >>> Hello. > >> I suspect that most people do not know what 'M365' is, would be good >> to explain. Am curious as to what 'M365' is! > > New branding and pricing(subscription) of MS Office. > > Microsoft 365 > https://www.microsoft.com/en-us/microsoft-365 [...] Thanks, I use LibreOffice which is free and easier to use -- it runs on many O/S's including those from Micosoft. https://www.libreoffice.org/
On 25/07/22 12:31, Mladen Gogala wrote: > On 7/24/22 20:15, Gavin Flower wrote: >> I suspect that most people do not know what 'M365' is, would be good >> to explain. Am curious as to what 'M365' is! > > M365 is the latest member in the ArmaLite M-16 family of products. It > can be connected to database to track down the DBA who don't check > their backups. > [...] <chuckles>
On 7/24/22 17:27, Mladen Gogala wrote: > On 7/24/22 19:56, Taka Taka wrote: >> Hello. >> >> I posted question bellow. > > > And? No takers? I wonder why. Maybe the question is unclear? This is > really surprising :) The question was straight forward and clear. > >> >> Hello. >> I would like to know if psqlodbc_13_02 is compatible with M365. >> Also, could you please tell me which of the psqlodbc_13_02 would be >> suitable to Windows 10 64-bit? > > What is M365? Is it a part of Microsoft Office 365, aka "O365"? Is it > related to M-16? What di you mean by "driver suitable for Windows 10"? > If the driver can be installed and configured by the MS ODBC driver > administrator, then I guess it's suitable. Make sure the driver you use > is mauve, they take the least RAM The ODBC lacks the version matrix the JDBC site: https://jdbc.postgresql.org/download.html has so I think is appropriate to verify version compatibility. Though as I mentioned it probably a low work task to just try it. >> Was my question inappropriate? >> I wanted to know if the pdbc driver above would be compatible to >> Microsoft's M365. > What part of Office 365 do you want the compatibility with? Excel? Other parts of Office also use database connectivity such as Access or Word. >> Also, I find variety in the odbc driver. > > I don't. ODBC drivers implement the same protocol when communicating > with the database and they all work the same. Here is what I have: Hmm, I wonder why they have versions then? As to below, really? If you don't want to answer the question then don't. > > The string "f36" in the PostgreSQL ODBC package name denotes a very > special version of Windows, more advanced than even Windows 11. I was > able to connect all 3 of the drivers above to LibreOffice and use them > to query the underlying database. I was able to do the same on my > Windows 8.1, with all 3 of those drivers. > >> Is it possible to know which of the driver is suitable to Windows 10 >> 64-bit? > > Suitable how? What exactly do you want to do? What does the word > "suitable" even mean in the context you're using it? > >> Or could you please tell me where to inquire? >> > There is this site named "https://www.google.com" which can be used to > find a lot of useful information and some paid ads, too. As of lately, I > prefer DDG, but that's just a personal preference. > > If there were no takers for the first question, that may say something > about the question. At this point, you gotta ask yourself one question > only: do I feel lucky? > > -- > Mladen Gogala > Database Consultant > Tel: (347) 321-1217 > https://dbwhisperer.wordpress.com > -- Adrian Klaver adrian.klaver@aklaver.com
On 7/24/22 17:32, Gavin Flower wrote: > On 25/07/22 12:19, Adrian Klaver wrote: >> On 7/24/22 17:15, Gavin Flower wrote: >>> On 25/07/22 11:56, Taka Taka wrote: >>>> Hello. >> >>> I suspect that most people do not know what 'M365' is, would be good >>> to explain. Am curious as to what 'M365' is! >> >> New branding and pricing(subscription) of MS Office. >> >> Microsoft 365 >> https://www.microsoft.com/en-us/microsoft-365 > > [...] > > Thanks, I use LibreOffice which is free and easier to use -- it runs on > many O/S's including those from Micosoft. > https://www.libreoffice.org/ > That is what I use also. Unfortunately if you are in a true blue MS shop LibreOffice will only take you so far at which point you will need MS 365 to get things done. FYI, MS 365 is MS looking at Apple and realizing that they needed to convert to having users generate a continuous revenue stream instead of having them hang on to site licensed copy for years. -- Adrian Klaver adrian.klaver@aklaver.com
Other parts of Office also use database connectivity such as Access or Word.Also, I find variety in the odbc driver.
I don't. ODBC drivers implement the same protocol when communicating with the database and they all work the same. Here is what I have:
Hmm, I wonder why they have versions then?
Good question. One part of the story are package versions, bug fixes and such. However, I think that your question was about the versions of the ODBC protocol. This may answer it:
https://en.wikipedia.org/wiki/Open_Database_Connectivity
Version history
Version history:[22]
- 1.0: released in September 1992[23]
- 2.0: c. 1994
- 2.5
- 3.0: c. 1995, John Goodson of Intersolv and Frank Pellow and Paul Cotton of IBM provided significant input to ODBC 3.0[24]
- 3.5: c. 1997
- 3.8: c. 2009, with Windows 7[25]
- 4.0: Development announced June 2016[26] with first implementation with SQL Server 2017 released Sep 2017 and additional desktop drivers late 2018 [27] final spec on Github
By the way, version 4 of the protocol supports "fast_executemany":
https://dbwhisperer.wordpress.com/2020/11/21/pyodbc-fast_executemany-and-oracle-rdbms/
MS SQL ODBC 1.7 and Oracle Instant Client 19.9 ODBC drivers and newer do support "fast_executemany". PostgreSQL ODBC 13 does not. Here is the table:
https://github.com/mkleehammer/pyodbc/wiki/fast_executemany-support-for-various-ODBC-drivers
As to below, really? If you don't want to answer the question then don't.
Boys just wanna have fun. This is a shameless plug of the famous Cindy Lauper's song, but you get the picture, don't you? To my credit, I didn't answer the 1st one. Tonight, I've been socializing with Sam Adams, so I replied. When someone who doesn't know how to properly write "O365" asks about "how suitable ODBC driver is", then I feel entitled to little fun.
Now, since you don't appear to be a fan of my particular variety of humor, can you possibly translate the question and explain to me what a "suitable driver" is and what is M365? If you manage to prove to me that the question makes sense, I will apologize to the OP and offer you a pint of Sam Adams as an apology for my bad behavior. On the other hand, if the question doesn't make sense, I will gladly accept the same from you.
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com
On 7/24/22 18:14, Mladen Gogala wrote: > Answers in-line: > > https://dbwhisperer.wordpress.com/2020/11/21/pyodbc-fast_executemany-and-oracle-rdbms/ > > MS SQL ODBC 1.7 and Oracle Instant Client 19.9 ODBC drivers and newer do > support "fast_executemany". PostgreSQL ODBC 13 does not. Here is the table: > > https://github.com/mkleehammer/pyodbc/wiki/fast_executemany-support-for-various-ODBC-drivers > > >> >> As to below, really? If you don't want to answer the question then >> don't. > > Boys just wanna have fun. This is a shameless plug of the famous Cindy > Lauper's song, but you get the picture, don't you? To my credit, I > didn't answer the 1st one. Tonight, I've been socializing with Sam > Adams, so I replied. When someone who doesn't know how to properly write > "O365" asks about "how suitable ODBC driver is", then I feel entitled to > little fun. > > Now, since you don't appear to be a fan of my particular variety of > humor, can you possibly translate the question and explain to me what a > "suitable driver" is and what is M365? If you manage to prove to me that 1) Looking at the email of the OP would provide information that there might be a language barrier involved. And I who have been known to be less then clear in the one language I know, attempt to be forgiving of those that are trying to get a thought across in a foreign language. 2) Suitable driver is just that a driver that will suit the needs of working on Windows 10 with MS Office/Office/Microsoft 365. I am not sure how that could be made any clearer. 3) "...compatible to Microsoft's M365." I who am not a Windows user, knew what the OP meant. And if you go here: https://en.wikipedia.org/wiki/Microsoft_365#As_%22Microsoft_365%22 You will see: "On March 30, 2020, Microsoft announced that the consumer plans of Office 365 would be rebranded as "Microsoft 365" (a brand also used by Microsoft for an enterprise subscription bundle of Windows, Office 365, and security services) on April 21, 2020, succeeding existing consumer plans of Office 365." So M365 is actually more correct then 0365. > the question makes sense, I will apologize to the OP and offer you a > pint of Sam Adams as an apology for my bad behavior. On the other hand, > if the question doesn't make sense, I will gladly accept the same from you. > > -- > Mladen Gogala > Database Consultant > Tel: (347) 321-1217 > https://dbwhisperer.wordpress.com > -- Adrian Klaver adrian.klaver@aklaver.com
3) "...compatible to Microsoft's M365." I who am not a Windows user,
knew what the OP meant. And if you go here:
https://en.wikipedia.org/wiki/Microsoft_365#As_%22Microsoft_365%22
You will see:
"On March 30, 2020, Microsoft announced that the consumer plans of
Office 365 would be rebranded as "Microsoft 365" (a brand also used by
Microsoft for an enterprise subscription bundle of Windows, Office 365,
and security services) on April 21, 2020, succeeding existing consumer
plans of Office 365."
So M365 is actually more correct then 0365.
Suitable driver is just that a driver that will suit the needs of working on Windows 10 with MS Office/Office/Microsoft 365.
Literally every ODBC driver on Windows fits this definition. That is the purpose of ODBC: having a uniform set of calls for various databases. That is why people still use it, even on Linux. And yes, like you, I am a Linux user too.
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com
On 2022-07-24 20:27:56 -0400, Mladen Gogala wrote: > On 7/24/22 19:56, Taka Taka wrote: > I would like to know if psqlodbc_13_02 is compatible with M365. > Also, could you please tell me which of the psqlodbc_13_02 would be > suitable to Windows 10 64-bit? > > What is M365? Is it a part of Microsoft Office 365, aka "O365"? Is it related > to M-16? What di you mean by "driver suitable for Windows 10"? If the driver > can be installed and configured by the MS ODBC driver administrator, then I > guess it's suitable. Not at all. There are 32 bit and 64 bit variants. You can install and configure both on a 64 bit Windows, but you can only use the one which matches the architecture of your application. I am guessing that M365 is now 64 bit only, but I've certainly seen 32 bit MS Office installed on 64 bit MS Windows, and the confusion that caused. Also there is a Unicode and an "ANSI" variant of the PostgreSQL ODBC driver. My advice has always been to use the Unicode variant, but I assume that the ANSI variant still exists because some (legacy) Windows applications can't deal with Unicode. So while I'm fairly confident that the answer to Taka's answer is "64 bit, Unicode", I see that this might not be so obvious to them. > Also, I find variety in the odbc driver. > > I don't. ODBC drivers implement the same protocol when communicating with the > database and they all work the same. Actually, no: The protocol between the application and the driver is the same (for a given platform and ODBC version), but the protoocl between the driver and the database is different: > Here is what I have: > > [mgogala@umajor ~]$ rpm -qa *odbc* > oracle-instantclient-odbc-21.5.0.0.0-1.x86_64 > postgresql-odbc-13.01.0000-2.fc36.x86_64 > msodbcsql17-17.10.1.1-1.x86_64 That's why you have three different drivers. You can't use the oracle driver to connect to a postgresql database. You may not even be able to use an oracle driver to connect to an oracle database that's too old or too new (or you may be able to connect and then get weird errors - BTDT). PostgreSQL is in my experience rather tolerant of client/server mismatches, but I wouldn't be surprised if some stuff wouldn't work if the versions are too different. Also, an application written for ODBC 4.0 might not work with a driver implementing ODBC 3.8. hp -- _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp@hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!"