You can subscribe to this list here.
2004 |
Jan
|
Feb
(3) |
Mar
(8) |
Apr
(1) |
May
(3) |
Jun
(4) |
Jul
(11) |
Aug
(7) |
Sep
|
Oct
(7) |
Nov
(29) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(1) |
Feb
(7) |
Mar
(4) |
Apr
(3) |
May
(8) |
Jun
|
Jul
|
Aug
(6) |
Sep
(2) |
Oct
(5) |
Nov
(5) |
Dec
(1) |
2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
(6) |
May
(2) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
(5) |
Nov
(3) |
Dec
|
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(8) |
May
(3) |
Jun
(1) |
Jul
(8) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
(1) |
Feb
|
Mar
|
Apr
(7) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(4) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2011 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
(8) |
May
|
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
(12) |
Mar
|
Apr
(7) |
May
(8) |
Jun
(3) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Theodore P. <te...@ya...> - 2004-11-15 12:57:26
|
Theodore, I have been a postgresql user for over 5 years. Many times I have tried to get ODBC working and failed. I read the articles and saw it reported that others did get it to work so I plugged on. One article at: http://www.macdevcenter.com/pub/a/mac/2003/07/25/odbc.html said that the he got ODBC to work with slight problems. The best that I have been able to do, is to duplicat what was said in the article. I have a working ODBC connection from excel to postgres except the inspector is blank. I can write my SQL as long as I know the column names and relationships. I see from the psqlODBC list that there is some activity trying to correct some problems. I do not know it the problem is with psqlODBC or IODBC. My solution was to abadon ODBC in favor of libpq and link against the C libraries. Best of luck... I will continue to read of your trials.... Ted > Hi people, > > I'm a bit new to ODBC, although I've played with it > some. I'd like to > know, what did people use before iODBC arrived for > the Mac? I mean, > many applications have a need to use multiple > databases, especially > when the application is not an "in-house" > application (an app in the > horizontal markets). > > For these cases, how did they do it? > > Also, does anyone know if Apple have plans on > documenting their iODBC a > bit better? Or what about plans for including more > drivers by default? > That would greatly ease the use of databases. For > example, many printer > drivers come installed by default on MacOSX, so why > not ODBC drivers? > Printers and databases, as an analogy, often works > very well! > > Right now I'm having to use MS's ODBC documentation, > which while OK, I > would definitely expect Apple's documentation to be > better ;o) > > -- > Theodore H. Smith - Software Developer. > http://www.elfdata.com > > > __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com |
From: Tim H. <th...@op...> - 2004-11-15 09:44:03
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Theodore H.Smith wrote: | Why is the driver software download 34.5MB when compressed? Thats a bit | much. | | How big is the driver executable once the rest is discounted? Hi, Which driver are you downloading in particular? Typically the downloads include documentation and sample applications; as appropriate, the multi-tier ones come in separate client and server parts, where the server contains broker & agent components (and web-based setup GUI). HTH, ~Tim - -- Tim Haynes Product Development Consultant OpenLink Software <http://www.openlinksw.com/> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFBmHpQ+gVZmutkHqERAjVUAKCdGD76L0HTxv0hz3+/l+SQi9x+SgCbBglL WmTEccG7fGJmvyy6rtfuOpQ= =DgOS -----END PGP SIGNATURE----- |
From: Tim H. <th...@op...> - 2004-11-15 09:37:42
|
Theodore H.Smith wrote: > I'm not sure about some of the keywords used, as I'm still finding my > way around this area. Whats the difference between single-tier and > multi-tier. The only usage of the "tier" I've seen, has been for the > number of layers in a database system. Pretty much all applications are > multi-tier from this aspect, so I'd be surprised if you were selling a > single tier ODBC driver, because that wouldn't really make sense. The > GUI is considered a "tier" in that use of the word. > So obviously I don't know the sense of the word "tier" you are using. > What does it mean? Hi, It's more about the number of "connection"s employed to achieve the final connection to the database within the ODBC infrastructure employed (ie, the application is taken for granted). single-tier: app -> driver manager -> driver -> RDBMS native comms layer* -> database (TCP/IP or shared memory) multli-tier: app -> driver manager -> driver -> RPC layer* -> server box -> RDBMS native comms layer* -> database (TCP/IP or shared memory) (`*' marks a connection, be it over tcp/ip or shared memory, between components.) > The pricing is not directly displayed on your website, and I need to go > through the confusing order page first to find out how much would it > cost. I can't seem to find your licencing information, also. The website is currently being redesigned, where I gather these problems will be addressed. HTH, ~Tim -- Tim Haynes Product Development Consultant OpenLink Software <http://www.openlinksw.com/> |
From: Tim H. <th...@op...> - 2004-11-15 09:23:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Theodore H.Smith wrote: | Hi Jonathan, | | I have a simple question. I'm trying to figure out the DSN connect | string. I'm using the standard iodcbtest.c file by iODCB. | | I tried entering this connect string into the iODBC test app compiled | from iodbctest.c | | "Driver= /usr/local/lib/psqlodbc.so;Database=test;Server=localhost; | Type=PostgreSQL;UID=postgres;PWD=pass" | | The password is not the original, but apart from that it's exactly | as-is. Well, it told me this: | | [iODBC][Driver Manager]Specified driver could not be loaded, | SQLSTATE=IM003 | [iODBC][Driver Manager]No such file or directory, SQLSTATE=00000 | | So, apparantly it can't find the driver and it can't find the database | file! What now? Sorry I'm rather new to ODBC, as you can tell. Hi, There are no spaces on the left of the `='. A quick test here inserting a space reproduces your error. HTH, ~Tim - -- Tim Haynes Product Development Consultant OpenLink Software <http://www.openlinksw.com/> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFBmHV6+gVZmutkHqERAlvYAKC+OGgqgWmJa5kZgX5+F/outHAM5QCfRVho iSY0ApOTX967YrT3IwVbxPI= =96sE -----END PGP SIGNATURE----- |
From: Theodore H. S. <de...@el...> - 2004-11-14 11:11:39
|
How well do most databases work with UTF-8? I see a lot of "Unicode" functions for some databases. The thing is, many of these functions are based around the misconception that Unicode = UCS2. IE, that a Unicode letter takes 2 bytes long, and only two bytes long. Firstly, UCS2 is not part of Unicode. UTF-16 is, but UTF-16 can be 2 or 4 bytes. Secondly, it only has UCS2 support, not UTF-8, or UTF-32 support. While most people can skip UTF-32 safely, UTF-8 is becoming the Unicode format of choice these days. Mostly, because it is byte oriented. It never has a \0 byte in its data, except in the same places that ASCII does. So I'm wondering, how well do databases in general deal with UTF-8? Usually, you can treat UTF-8 as just Latin1. That is, its just a sequence of bytes, that can have their high-bit set. I suppose that if a database could store latin-1, then it can store UTF-8, right? For that reason, I'm a bit dissapointed that more database documentation doesn't mention the advantage of UTF-8 over UTF-16, and also doesn't mention that the "Unicode" database functionality is actually unnecessary to store Unicode. |
From: Theodore H. S. <de...@el...> - 2004-11-13 23:39:38
|
Hi Hugh, Thanks for pointing me to the docs, I was unaware of these. I found out that iodbctest worked fine. In fact, I had trouble with odbctest that was located in '/Library/Application Support/iodbc/bin' and the standard installed Jaguar odbctest. I will read the documents now. Sorry for the huge volume of mail I sent. I still have some problems, but I'll read the docs before asking them. > As I stated to you from the outset, the ODBC components Apple bundles > with > their OS simply will *NOT* work with Framework based ODBC drivers, > thus you > should not be linking nor testing drivers against any of their > components. > If you are linking the Postgres driver you compiled against the Apple > ODBC > components then this would explain why this does not work also. Right. I actually didn't specify any linking with that open source Postgres driver, I just compiled it with configure;make;make install; So all the linking is the default specified by the makefile. Unfortunately makefiles and configure is something I know little about, I'm a CodeWarrior guy myself. > We have been > pro-actively trying to get Apple to resolve this issue by either > bundling > the iODBC components we build and most other ODBC vendors (both > Application > and Driver) in the ODBC space on the Mac use, but to date this seems > to be > falling on deaf ears their for reasons unknown to us. Probably the dilemma of the Universe. Can you imagine a perfect world? Most can't. It would be nice to see Apple take ODBC seriously. Documentation, better support, maybe even actively working on the ODBC open source code. Actually, I'd like to see Apple take data base (in general) for the Mac seriously. > I would strongly suggest you read some of the documentation on our WEB > site > on these issues and proceed accordingly: > > http://www.iodbc.org/index.php?page=docs/macosodbcstory/index > http://docs.openlinksw.com/st/osxliteconf.html > http://support.openlinksw.com/support/mac-faq.html > http://support.openlinksw.com/support/tutorials.vsp?c=mac Great. I'll read these up. |
From: Hugh W. <hwi...@op...> - 2004-11-13 21:20:52
|
Hi Theodore, If as implied you are using the 'odbctest' program located in '/usr/bin' then this is the Apple provided program which is not Framework based and build from an old iODBC 3.0.6 version, then this simply will not work with the Framework based drivers provided by OpenLink and Actual. The iODBC Driver Manager provided by OpenLink which the Actual ODBC drivers also use provides a test program called iodbctest located in '/Library/Application Support/iodbc/bin' and this is the program you should be using to test these drivers. Thus try using this and both the OpenLink and Actual drivers will work. As I stated to you from the outset, the ODBC components Apple bundles with their OS simply will *NOT* work with Framework based ODBC drivers, thus you should not be linking nor testing drivers against any of their components. If you are linking the Postgres driver you compiled against the Apple ODBC components then this would explain why this does not work also. We have been pro-actively trying to get Apple to resolve this issue by either bundling the iODBC components we build and most other ODBC vendors (both Application and Driver) in the ODBC space on the Mac use, but to date this seems to be falling on deaf ears their for reasons unknown to us. I would strongly suggest you read some of the documentation on our WEB site on these issues and proceed accordingly: http://www.iodbc.org/index.php?page=docs/macosodbcstory/index http://docs.openlinksw.com/st/osxliteconf.html http://support.openlinksw.com/support/mac-faq.html http://support.openlinksw.com/support/tutorials.vsp?c=mac Best Regards, Hugh Williams OpenLink Software Web: http://www.openlinksw.com Universal Data Access & Data Integration Technology Providers -----Original Message----- From: iod...@li... [mailto:iod...@li...] On Behalf Of Theodore H.Smith Sent: 13 November 2004 17:08 To: iod...@li... Subject: [Iodbc-macosx] odbctest? I tried using the odbctest tool. I saw this: "Enter ODBC connect string (? shows list, or DSN=...): ?" I pressed ? as suggested, to get a list of DSN's, but was presented with nothing. I've installed Postgres from OpenLink, and within the ODBC Admin tool, I pressed "Test", and it said that the connection is working fine, and I can use it now. It told me that the DSN "olpsql" was working successfully. So why does odbctest not agree?? This isn't working very smoothly, so far. I really need this to be smooth for my application. ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Iodbc-macosx mailing list Iod...@li... https://lists.sourceforge.net/lists/listinfo/iodbc-macosx |
From: Theodore H. S. <de...@el...> - 2004-11-13 18:40:35
|
I tried odbctest with actual's postgres drivers. I was impressed with the cleanness, smoothness and simplicity of actual's installer and download process. However, it told me that it's test completed, even though I entered an invalid password (on purpose!). I tried out odbctest then, and it still failed :o( Typing ? into odbctest displays no drivers. This isn't going well. What is wrong? ODBCTest? Is that the problem? What is wrong? |
From: Theodore H. S. <de...@el...> - 2004-11-13 17:51:17
|
I tried replacing my password with a bad one, and I was still told "The connection DSN was tested successfully". Then I tried deleting both the user name, and the password, and I was still told "The connection DSN was tested successfully?" Obviously, this "test" is not very good. So I still have a problem here, and I can't find any information telling me what I'm supposed to do. |
From: Theodore H. S. <de...@el...> - 2004-11-13 17:21:48
|
So, I tried running odbctest and entering this string: DSN=olpsql;UID=postgres;PWD=XXX It still fails, despite that the ODBC Admin tells me that it doesn't fail. Also, odbctest still displays no drivers available! Whats going on? |
From: Theodore H. S. <de...@el...> - 2004-11-13 17:08:49
|
I tried using the odbctest tool. I saw this: "Enter ODBC connect string (? shows list, or DSN=...): ?" I pressed ? as suggested, to get a list of DSN's, but was presented with nothing. I've installed Postgres from OpenLink, and within the ODBC Admin tool, I pressed "Test", and it said that the connection is working fine, and I can use it now. It told me that the DSN "olpsql" was working successfully. So why does odbctest not agree?? This isn't working very smoothly, so far. I really need this to be smooth for my application. |
From: Theodore H. S. <de...@el...> - 2004-11-13 16:33:33
|
Hi Jonathan, I have a simple question. I'm trying to figure out the DSN connect string. I'm using the standard iodcbtest.c file by iODCB. I tried entering this connect string into the iODBC test app compiled from iodbctest.c "Driver= /usr/local/lib/psqlodbc.so;Database=test;Server=localhost; Type=PostgreSQL;UID=postgres;PWD=pass" The password is not the original, but apart from that it's exactly as-is. Well, it told me this: [iODBC][Driver Manager]Specified driver could not be loaded, SQLSTATE=IM003 [iODBC][Driver Manager]No such file or directory, SQLSTATE=00000 So, apparantly it can't find the driver and it can't find the database file! What now? Sorry I'm rather new to ODBC, as you can tell. There is actually a file at /usr/local/lib/psqlodbc.so I got this file by compiling the psql odbc tool. I was told this on the install, but what I'm meant to do with that information, I don't know! I'm also confused with the LIBDIR thing. /usr/bin/install -c .libs/psqlodbc.so /usr/local/lib/psqlodbc.so /usr/bin/install -c .libs/psqlodbc.lai /usr/local/lib/psqlodbc.la ---------------------------------------------------------------------- Libraries have been installed in: /usr/local/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `DYLD_LIBRARY_PATH' environment variable during execution See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- /bin/sh ./mkinstalldirs /usr/local/share/psqlodbc mkdir -p -- /usr/local/share/psqlodbc /usr/bin/install -c -m 644 odbc.sql /usr/local/share/psqlodbc/odbc.sql /usr/bin/install -c -m 644 odbc-drop.sql /usr/local/share/psqlodbc/odbc-drop.sql On 12 Nov 2004, at 22:41, Jonathan Monroe wrote: > > On Nov 12, 2004, at 2:20 PM, Theodore H. Smith wrote: > >> >> On 12 Nov 2004, at 15:19, Jonathan Monroe wrote: >> >>>> Right now I'm having to use MS's ODBC documentation, which while >>>> OK, I would definitely expect Apple's documentation to be better >>>> ;o) >>> >>> You're right that Apple's technical documentation is generally >>> better. However, ODBC is a Microsoft technology, and their >>> documentation is pretty good. For the most part, what you'll find >>> on MSDN also applies to iODBC. If you'd like an example project >>> file to help you get going, send me an e-mail offline and I'll be >>> happy to send one to you. Just let me know which compiler and >>> language you'd like to use. >> >> Thanks, if I ever do need that, I'll ask. For the moment I'm OK with >> MS's docs, though. >> > > OK, great. Please don't hesitate to contact me if you have any > questions or if there's anything else I can do for you. > > Best regards, > > Jonathan Monroe > Actual Technologies - ODBC for OS X > mo...@ac... > > > |
From: Jonathan M. <id...@ac...> - 2004-11-13 04:56:16
|
On Nov 12, 2004, at 8:50 PM, Hugh Williams wrote: > Having said that I do think you have a point in terms of providing an > implementation similar to that done on Mac Classic, which we could > consider, > although this is something that should be done in consultation with > Apple > themselves in terms of location I feel, but we have not found them > particualrly keen to promote/enhance ODBC on MacOSX in general. We have found Apple to be quite pragmatic and earnest about improving ODBC on the Mac. I expect there to be noticeable improvements in ODBC support in future releases of the OS. Jonathan Monroe Actual Technologies - ODBC for OS X http://www.actualtechnologies.com mo...@ac... On Nov 12, 2004, at 8:50 PM, Hugh Williams wrote: > Hi Theodore, > > The iODBC port on MacOSX is based on a Unix/Windows type port were ODBC > originated and in those realms user are allowed to instal their ODBC > Drivers > in a location of their choice. Note also that MacOSX at its core is > essentially a Unix based system as you have seen when building the > Postgres > driver. Apple themselves adopted this approach when developing their > ODBC > Administrator which is not even Framework based. > Having said that I do think you have a point in terms of providing an > implementation similar to that done on Mac Classic, which we could > consider, > although this is something that should be done in consultation with > Apple > themselves in terms of location I feel, but we have not found them > particualrly keen to promote/enhance ODBC on MacOSX in general. > > As Johnathan Monroe stated in his posting you can always create a > DSN-Less > connection to avoid having to configure an ODBC DSN in the > Administrator, > provided you know what parameters required for the specified driver. > > Best Regards, > Hugh Williams > OpenLink Software > Web: http://www.openlinksw.com > Universal Data Access & Data Integration Technology Providers > > -----Original Message----- > From: iod...@li... > [mailto:iod...@li...] On Behalf Of Theodore > H.Smith > Sent: 12 November 2004 23:59 > To: iod...@li... > Subject: [Iodbc-macosx] Auto-scanning and simpler process for end-users > > Will iODBC ever auto-scan a particular folder for libraries? > > To me, that seems the most sensible thing to do. That way, we wouldn't > even > need the iODBC admin folder. Many other MacOS technologies work this > way, > just by putting a file in a certain folder it is used by the system. > Its a > much nicer way. > > Also, I'm a bit new to this data source name thing, I don't quite get > it > yet. Must I register every database with a DSN in the admin? > > Can ODCB just use the regular access name? That would be much easier. > EG something like this: > > DataBaseConnection = SomeODBCConnectFunction( "127.0.0.1 username > password > databasename" ); > > That way, I wouldn't need to set up any DSN in the iODCB admin. > > I'm just thinking of the end-user. They'd like everything to be as > simple as > possible, so it is preferable to avoid asking the end-user to fiddle > around > with the iODCB admin. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS > DOWNLOAD - > A multidimensional database that combines robust object and relational > technologies, making it a perfect match for Java, C++,COM, XML, ODBC > and > JDBC. www.intersystems.com/match8 > _______________________________________________ > Iodbc-macosx mailing list > Iod...@li... > https://lists.sourceforge.net/lists/listinfo/iodbc-macosx > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE > FREE OODBMS DOWNLOAD - A multidimensional database that combines > robust object and relational technologies, making it a perfect match > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > _______________________________________________ > Iodbc-macosx mailing list > Iod...@li... > https://lists.sourceforge.net/lists/listinfo/iodbc-macosx > |
From: Hugh W. <hwi...@op...> - 2004-11-13 02:50:18
|
Hi Theodore, The iODBC port on MacOSX is based on a Unix/Windows type port were ODBC originated and in those realms user are allowed to instal their ODBC Drivers in a location of their choice. Note also that MacOSX at its core is essentially a Unix based system as you have seen when building the Postgres driver. Apple themselves adopted this approach when developing their ODBC Administrator which is not even Framework based. Having said that I do think you have a point in terms of providing an implementation similar to that done on Mac Classic, which we could consider, although this is something that should be done in consultation with Apple themselves in terms of location I feel, but we have not found them particualrly keen to promote/enhance ODBC on MacOSX in general. As Johnathan Monroe stated in his posting you can always create a DSN-Less connection to avoid having to configure an ODBC DSN in the Administrator, provided you know what parameters required for the specified driver. Best Regards, Hugh Williams OpenLink Software Web: http://www.openlinksw.com Universal Data Access & Data Integration Technology Providers -----Original Message----- From: iod...@li... [mailto:iod...@li...] On Behalf Of Theodore H.Smith Sent: 12 November 2004 23:59 To: iod...@li... Subject: [Iodbc-macosx] Auto-scanning and simpler process for end-users Will iODBC ever auto-scan a particular folder for libraries? To me, that seems the most sensible thing to do. That way, we wouldn't even need the iODBC admin folder. Many other MacOS technologies work this way, just by putting a file in a certain folder it is used by the system. Its a much nicer way. Also, I'm a bit new to this data source name thing, I don't quite get it yet. Must I register every database with a DSN in the admin? Can ODCB just use the regular access name? That would be much easier. EG something like this: DataBaseConnection = SomeODBCConnectFunction( "127.0.0.1 username password databasename" ); That way, I wouldn't need to set up any DSN in the iODCB admin. I'm just thinking of the end-user. They'd like everything to be as simple as possible, so it is preferable to avoid asking the end-user to fiddle around with the iODCB admin. ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Iodbc-macosx mailing list Iod...@li... https://lists.sourceforge.net/lists/listinfo/iodbc-macosx |
From: Jonathan M. <io...@ac...> - 2004-11-13 00:33:26
|
On Nov 12, 2004, at 5:58 PM, Theodore H.Smith wrote: > Will iODBC ever auto-scan a particular folder for libraries? > > To me, that seems the most sensible thing to do. That way, we wouldn't > even need the iODBC admin folder. Many other MacOS technologies work > this way, just by putting a file in a certain folder it is used by the > system. Its a much nicer way. iODBC on Mac Classic works that way. For some reason that functionality was dropped for the port to Mac OS X. > Also, I'm a bit new to this data source name thing, I don't quite get > it yet. Must I register every database with a DSN in the admin? > > Can ODCB just use the regular access name? That would be much easier. > EG something like this: > > DataBaseConnection = SomeODBCConnectFunction( "127.0.0.1 username > password databasename" ); > > That way, I wouldn't need to set up any DSN in the iODCB admin. Its certainly possible to create DSN-less connections. Using C and our driver for open source databases to connect to PostgreSQL, it would look something like this: char finalDSN[512]; int dsnLen; char dsn[] = "Driver= /Library/ODBC/atopnsrc.bundle/Contents/MacOS/atopnsrc;" "Database=my_database;" "Server=localhost;" "Type=PostgreSQL;" "UID=my_user_id;PWD=my_password"; retcode = SQLDriverConnect(con, NULL, dsn, SQL_NTS, finalDSN, dsnLen, SQL_DRIVER_NOPROMPT); The same thing can be done in REALbasic by setting the DataSource property of the ODBCDatabase class to the above string. > I'm just thinking of the end-user. They'd like everything to be as > simple as possible, so it is preferable to avoid asking the end-user > to fiddle around with the iODCB admin. With DSN-less connections, end users don't have to worry about the Administrator at all. Best regards, Jonathan Monroe Actual Technologies - ODBC for OS X http://www.actualtechnologies.com mo...@ac... |
From: Theodore H. S. <de...@el...> - 2004-11-12 23:59:09
|
Will iODBC ever auto-scan a particular folder for libraries? To me, that seems the most sensible thing to do. That way, we wouldn't even need the iODBC admin folder. Many other MacOS technologies work this way, just by putting a file in a certain folder it is used by the system. Its a much nicer way. Also, I'm a bit new to this data source name thing, I don't quite get it yet. Must I register every database with a DSN in the admin? Can ODCB just use the regular access name? That would be much easier. EG something like this: DataBaseConnection = SomeODBCConnectFunction( "127.0.0.1 username password databasename" ); That way, I wouldn't need to set up any DSN in the iODCB admin. I'm just thinking of the end-user. They'd like everything to be as simple as possible, so it is preferable to avoid asking the end-user to fiddle around with the iODCB admin. |
From: Theodore H. S. <de...@el...> - 2004-11-12 23:51:26
|
I've been trying to get to grips with the various ODBC drivers around. I thought I'd give Postgres a go. So, I downloaded it, and compiled. The compile went smoothly, which is good because it said it required Postgres 7.3 and it didn't give instructions on how to get it. It has now produced a few files. I don't really understand this message about LIBDIR. It is written in even more awkward English than my own, and even then I'm not sure what its saying. (Install message at end of email!) I'm also not sure what I'm supposed to do next to get access to this ODBC driver! I tried opening "OpenLink iODBC Admin", but it didn't automatically display them. There are so many files I'm not sure which file I'm supposed to add in the "ODBC Driver" pane. Postgres.org could have done a lot more to make this simple. Like for example, making a precompiled library and telling us where to put it, and what to enter into the iODBC Admin app! Anyhow, its all learning, once learnt I'll know the answer forever. /bin/sh ./libtool --mode=install /usr/bin/install -c psqlodbc.la /usr/local/lib/psqlodbc.la /usr/bin/install -c .libs/psqlodbc.so /usr/local/lib/psqlodbc.so /usr/bin/install -c .libs/psqlodbc.lai /usr/local/lib/psqlodbc.la ---------------------------------------------------------------------- Libraries have been installed in: /usr/local/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `DYLD_LIBRARY_PATH' environment variable during execution See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- /bin/sh ./mkinstalldirs /usr/local/share/psqlodbc mkdir -p -- /usr/local/share/psqlodbc /usr/bin/install -c -m 644 odbc.sql /usr/local/share/psqlodbc/odbc.sql /usr/bin/install -c -m 644 odbc-drop.sql /usr/local/share/psqlodbc/odbc-drop.sql |
From: Theodore H. S. <de...@el...> - 2004-11-12 21:05:19
|
Why is the driver software download 34.5MB when compressed? Thats a bit much. How big is the driver executable once the rest is discounted? |
From: Theodore H. S. <de...@el...> - 2004-11-12 20:59:00
|
> The Single-Tier drivers are general easy to install and get up and > running > as they only require installation on the single machine, although for > the > most part do require the installation of the database vendors client > networking software to comminicate with the remote database server How is this different than Multi-tier? Is it different in that the installation is not a product that is sold by you, but software that comes from the database vendor? Just trying to be clear here. > [Hugh] Bundle means you purchase a license allowing you to use any of > our > supported DataAccess API for the DB of interest ie ODBC, JDBC, ADO.Net > or > OLEDB, whereas seperately means you only purchase a license for only > one > DataAccess API ie ODBC or JDBC or ADO.Net or OLEDB . Seems I understood it wrong then, thanks for clarifying. > The pricing is not directly displayed on your website, and I need to go > through the confusing order page first to find out how much would it > cost. I > can't seem to find your licencing information, also. > > [Hugh] Base pricing and licence agreements etc is available from the > following URL: > > http://www.openlinksw.com/main/sales.htm Is it 99$ for a single tier driver? (per simultaneous connection of course) |
From: Theodore H. S. <de...@el...> - 2004-11-12 20:12:03
|
I hope asking about OpenLink isn't "offtopic" here. The companies are related so perhaps this is OK. The application I am working on, will need drivers installed on the client end only. What is the driver installation process? I notice something about "Type A" drivers for Oracle Single tier. They describe "Type A" as being some kind of preprocessor based thing where the SQL statements are put into the application source code. How does that make sense? If you are using ODBC, you are using ODBC, there are no preprocessors, you just call the ODBC API functions and thats the end of it. Are they suggesting we must change our code to use oracle drivers, thus negating all the benefits of ODBC??? I also need to know how does the installation process go. It needs to be as simple as possible. As for OEM and rebranding, it may be a possibility for the application, but I will need to discuss this with my superiors in the company first, so it might happen it might not happen. It might be good to get some information on the OEM/rebranding process first though, so I know what I'm talking about if the time ever comes that I should discuss it with them. |
From: Hugh W. <hwi...@op...> - 2004-11-12 20:11:34
|
Theodore, -----Original Message----- From: Theodore H. Smith [mailto:de...@el...] Sent: 12 November 2004 19:05 To: hwi...@op... Cc: iod...@li... Subject: Re: [Iodbc-macosx] What did people use before iODBC? Hello Hugh Williams, I'm not sure about some of the keywords used, as I'm still finding my way around this area. Whats the difference between single-tier and multi-tier. The only usage of the "tier" I've seen, has been for the number of layers in a database system. Pretty much all applications are multi-tier from this aspect, so I'd be surprised if you were selling a single tier ODBC driver, because that wouldn't really make sense. The GUI is considered a "tier" in that use of the word. [Hugh] The so called n-Tier architectures is a phrase coined around the time of the Client/Server era when applications (not just database systems) where being developed with a client and a server component to them. Thus if an application only required to be installed on the client machine it was termed Single-Tier (ST) and if on the client & server components (or even a gateway layer inbetween) it was call Multi-Tier (MT) (or n-Tier). As our DataAccess drivers for ODBC are available in both formats we label them accordingly. The Single-Tier drivers are general easy to install and get up and running as they only require installation on the single machine, although for the most part do require the installation of the database vendors client networking software to comminicate with the remote database server( not so in the case of the so called wire protocol driver which have this built in). Multi-Tier driver require the installation of a client and server component, but benefit from using our own communication layer for talking to the remote database server ie no DB client metworking required, and also as we have a server component with an Adminsitration and configuration file (our so called RuleBook) enable database access to be controlled on the server and this thus a more secure solution. So obviously I don't know the sense of the word "tier" you are using. What does it mean? [Hugh] As indicated above this is more in terms of the archicture of our DataAccess (ODBC, JDBC, ADO.Net, OLEDB) products. Which of the products would I be looking for? There are so many and once again, the keywords confuse me. Whats the difference between "Client Server" and "Application / Web Server"? I know what each one of those words mean, but in the context you put them and the combination you use them, it just doesn't seem to make sense. [Hugh] Depends on what your needs are. Client/Server model of licensing applicable when you have multiple descktop clients like say multiple Excel users that require connectivity directly to a Database server, and you can use the ST or MT drivers as you see fit. Application/Web Server model of licensing is applicable to when you have an Application or Web server environment in which client requests are funnelled through the Application or Web server which then connects to the database on their behalf, and once again you choose the appropriate ST or MT driver as you see fit. And whats the difference between the data access drive suite bundle, and "separately". I'm hoping it means that either you are selling them as a bundle, or together, but it took me a few minutes to figure this out, due to the insertion of a whole bunch of words in the middle, that threw me. Why not rephrase it as "Driver bundle" and "Drivers sold separately"? [Hugh] Bundle means you purchase a license allowing you to use any of our supported DataAccess API for the DB of interest ie ODBC, JDBC, ADO.Net or OLEDB, whereas seperately means you only purchase a license for only one DataAccess API ie ODBC or JDBC or ADO.Net or OLEDB . The pricing is not directly displayed on your website, and I need to go through the confusing order page first to find out how much would it cost. I can't seem to find your licencing information, also. [Hugh] Base pricing and licence agreements etc is available from the following URL: http://www.openlinksw.com/main/sales.htm I am not trying to be difficult, these are real problems I've experienced trying to get to grips with this. Its a bit opaque to me at the moment. [Hugh] Not a problem as DataAccess can be quite a daunting/confusing area for new users, thus we are happy to explain the intricases ... Regards, Hugh Williams On 12 Nov 2004, at 17:31, Hugh Williams wrote: > Hi Theodore, > > We at OpenLink Software have a wealth of knowledge regarding ODBC, > iODBC and the Mac having been working in the ODBC space since its > inception back in the early ninties, being the maintainer of the iODBC > OpenSource project (http://www.iodbc.org), and one if not the first > vendors to provide a suite of ODBC Drivers for the MacOSX platform. > > The iODBC Driver Manager offering from Apple is based the iODBC 3.0.6 > version from sometime ago which Apple have taken written their own > ODBC Administrator and now bundle with their OS. This ODBC Driver > Manager is Darwin (non-Framework based) version and in our experience > does not work as have others. With reagrds to ODBC documentation the > Microsoft documentation is as good as anym they beeing the original > authors of ODBC, there is nothing really for Apple to document apart > from their Mac specific Administration/Configuration tools. The iODBC > Web site also is a good reference source. > > OpenLink have their own iODBC Driver Manager and iODBC Adminstrator > based on the current iODBC release (3.52.1) which is also Framework > based for usage with Framework based ODBC drivers in addition to the > Darwin based ODBC Drivers. This if you are interested in ODBC Driver > for MacOSX you can obtain these from our Web site below as well as the > iODBC Driver Manager which is Free. > > With regards to how Database Applications where developed before ODBC > existed on Mac, much as on any other OS, they would have been > developed using the Database Vendors Native Call Level Interfaces and > hence only usable against that specific Database. One of the main > benefits of ODBC is that it enables application developers to write a > single application which can work against any backend database for > which a working ODBC driver is available. > > Hope this answers your questions ... > > Best Regards, > Hugh Williams > VP Product Development > OpenLink Software > Tel: +44 (0) 20 8681 7701 > Web: http://www.openlinksw.com > Universal Data Access & Data Integration Technology Providers > > -----Original Message----- > From: iod...@li... > [mailto:iod...@li...] On Behalf Of > Theodore H.Smith > Sent: 12 November 2004 10:12 > To: iod...@li... > Subject: [Iodbc-macosx] What did people use before iODBC? > > Hi people, > > I'm a bit new to ODBC, although I've played with it some. I'd like to > know, what did people use before iODBC arrived for the Mac? I mean, > many applications have a need to use multiple databases, especially > when the application is not an "in-house" application (an app in the > horizontal markets). > > For these cases, how did they do it? > > Also, does anyone know if Apple have plans on documenting their iODBC > a bit better? Or what about plans for including more drivers by > default? > That would greatly ease the use of databases. For example, many > printer drivers come installed by default on MacOSX, so why not ODBC drivers? > Printers and databases, as an analogy, often works very well! > > Right now I'm having to use MS's ODBC documentation, which while OK, I > would definitely expect Apple's documentation to be better ;o) > > -- > Theodore H. Smith - Software Developer. > http://www.elfdata.com > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE LinuxWorld > Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Iodbc-macosx mailing list > Iod...@li... > https://lists.sourceforge.net/lists/listinfo/iodbc-macosx > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Iodbc-macosx mailing list > Iod...@li... > https://lists.sourceforge.net/lists/listinfo/iodbc-macosx > > |
From: riders <de...@so...> - 2004-11-12 19:20:50
|
What is a Type A vs a Type B driver? |
From: Theodore H. S. <de...@el...> - 2004-11-12 19:05:01
|
Hello Hugh Williams, I'm not sure about some of the keywords used, as I'm still finding my way around this area. Whats the difference between single-tier and multi-tier. The only usage of the "tier" I've seen, has been for the number of layers in a database system. Pretty much all applications are multi-tier from this aspect, so I'd be surprised if you were selling a single tier ODBC driver, because that wouldn't really make sense. The GUI is considered a "tier" in that use of the word. So obviously I don't know the sense of the word "tier" you are using. What does it mean? Which of the products would I be looking for? There are so many and once again, the keywords confuse me. Whats the difference between "Client Server" and "Application / Web Server"? I know what each one of those words mean, but in the context you put them and the combination you use them, it just doesn't seem to make sense. And whats the difference between the data access drive suite bundle, and "separately". I'm hoping it means that either you are selling them as a bundle, or together, but it took me a few minutes to figure this out, due to the insertion of a whole bunch of words in the middle, that threw me. Why not rephrase it as "Driver bundle" and "Drivers sold separately"? The pricing is not directly displayed on your website, and I need to go through the confusing order page first to find out how much would it cost. I can't seem to find your licencing information, also. I am not trying to be difficult, these are real problems I've experienced trying to get to grips with this. Its a bit opaque to me at the moment. On 12 Nov 2004, at 17:31, Hugh Williams wrote: > Hi Theodore, > > We at OpenLink Software have a wealth of knowledge regarding ODBC, > iODBC > and the Mac having been working in the ODBC space since its inception > back > in the early ninties, being the maintainer of the iODBC OpenSource > project > (http://www.iodbc.org), and one if not the first vendors to provide a > suite > of ODBC Drivers for the MacOSX platform. > > The iODBC Driver Manager offering from Apple is based the iODBC 3.0.6 > version from sometime ago which Apple have taken written their own ODBC > Administrator and now bundle with their OS. This ODBC Driver Manager is > Darwin (non-Framework based) version and in our experience does not > work as > have others. With reagrds to ODBC documentation the Microsoft > documentation > is as good as anym they beeing the original authors of ODBC, there is > nothing really for Apple to document apart from their Mac specific > Administration/Configuration tools. The iODBC Web site also is a good > reference source. > > OpenLink have their own iODBC Driver Manager and iODBC Adminstrator > based on > the current iODBC release (3.52.1) which is also Framework based for > usage > with Framework based ODBC drivers in addition to the Darwin based ODBC > Drivers. This if you are interested in ODBC Driver for MacOSX you can > obtain > these from our Web site below as well as the iODBC Driver Manager > which is > Free. > > With regards to how Database Applications where developed before ODBC > existed on Mac, much as on any other OS, they would have been developed > using the Database Vendors Native Call Level Interfaces and hence only > usable against that specific Database. One of the main benefits of > ODBC is > that it enables application developers to write a single application > which > can work against any backend database for which a working ODBC driver > is > available. > > Hope this answers your questions ... > > Best Regards, > Hugh Williams > VP Product Development > OpenLink Software > Tel: +44 (0) 20 8681 7701 > Web: http://www.openlinksw.com > Universal Data Access & Data Integration Technology Providers > > -----Original Message----- > From: iod...@li... > [mailto:iod...@li...] On Behalf Of Theodore > H.Smith > Sent: 12 November 2004 10:12 > To: iod...@li... > Subject: [Iodbc-macosx] What did people use before iODBC? > > Hi people, > > I'm a bit new to ODBC, although I've played with it some. I'd like to > know, > what did people use before iODBC arrived for the Mac? I mean, many > applications have a need to use multiple databases, especially when the > application is not an "in-house" application (an app in the horizontal > markets). > > For these cases, how did they do it? > > Also, does anyone know if Apple have plans on documenting their iODBC > a bit > better? Or what about plans for including more drivers by default? > That would greatly ease the use of databases. For example, many printer > drivers come installed by default on MacOSX, so why not ODBC drivers? > Printers and databases, as an analogy, often works very well! > > Right now I'm having to use MS's ODBC documentation, which while OK, I > would > definitely expect Apple's documentation to be better ;o) > > -- > Theodore H. Smith - Software Developer. > http://www.elfdata.com > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE LinuxWorld > Reader's > Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Iodbc-macosx mailing list > Iod...@li... > https://lists.sourceforge.net/lists/listinfo/iodbc-macosx > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Iodbc-macosx mailing list > Iod...@li... > https://lists.sourceforge.net/lists/listinfo/iodbc-macosx > > |
From: Hugh W. <hwi...@op...> - 2004-11-12 17:31:50
|
Hi Theodore, We at OpenLink Software have a wealth of knowledge regarding ODBC, iODBC and the Mac having been working in the ODBC space since its inception back in the early ninties, being the maintainer of the iODBC OpenSource project (http://www.iodbc.org), and one if not the first vendors to provide a suite of ODBC Drivers for the MacOSX platform. The iODBC Driver Manager offering from Apple is based the iODBC 3.0.6 version from sometime ago which Apple have taken written their own ODBC Administrator and now bundle with their OS. This ODBC Driver Manager is Darwin (non-Framework based) version and in our experience does not work as have others. With reagrds to ODBC documentation the Microsoft documentation is as good as anym they beeing the original authors of ODBC, there is nothing really for Apple to document apart from their Mac specific Administration/Configuration tools. The iODBC Web site also is a good reference source. OpenLink have their own iODBC Driver Manager and iODBC Adminstrator based on the current iODBC release (3.52.1) which is also Framework based for usage with Framework based ODBC drivers in addition to the Darwin based ODBC Drivers. This if you are interested in ODBC Driver for MacOSX you can obtain these from our Web site below as well as the iODBC Driver Manager which is Free. With regards to how Database Applications where developed before ODBC existed on Mac, much as on any other OS, they would have been developed using the Database Vendors Native Call Level Interfaces and hence only usable against that specific Database. One of the main benefits of ODBC is that it enables application developers to write a single application which can work against any backend database for which a working ODBC driver is available. Hope this answers your questions ... Best Regards, Hugh Williams VP Product Development OpenLink Software Tel: +44 (0) 20 8681 7701 Web: http://www.openlinksw.com Universal Data Access & Data Integration Technology Providers -----Original Message----- From: iod...@li... [mailto:iod...@li...] On Behalf Of Theodore H.Smith Sent: 12 November 2004 10:12 To: iod...@li... Subject: [Iodbc-macosx] What did people use before iODBC? Hi people, I'm a bit new to ODBC, although I've played with it some. I'd like to know, what did people use before iODBC arrived for the Mac? I mean, many applications have a need to use multiple databases, especially when the application is not an "in-house" application (an app in the horizontal markets). For these cases, how did they do it? Also, does anyone know if Apple have plans on documenting their iODBC a bit better? Or what about plans for including more drivers by default? That would greatly ease the use of databases. For example, many printer drivers come installed by default on MacOSX, so why not ODBC drivers? Printers and databases, as an analogy, often works very well! Right now I'm having to use MS's ODBC documentation, which while OK, I would definitely expect Apple's documentation to be better ;o) -- Theodore H. Smith - Software Developer. http://www.elfdata.com ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Iodbc-macosx mailing list Iod...@li... https://lists.sourceforge.net/lists/listinfo/iodbc-macosx |
From: Jonathan M. <io...@ac...> - 2004-11-12 15:19:41
|
On Nov 12, 2004, at 4:11 AM, Theodore H.Smith wrote: > Hi people, > > I'm a bit new to ODBC, although I've played with it some. I'd like to > know, what did people use before iODBC arrived for the Mac? I mean, > many applications have a need to use multiple databases, especially > when the application is not an "in-house" application (an app in the > horizontal markets). > > For these cases, how did they do it? Mac OS X arguably became a mainstream OS with 10.2. I'd say that before 10.2, most people used OS 9. 10.2 was also when Apple started shipping the iODBC libraries with the OS. Mac OS 7 / 8 / 9 has a long history with ODBC going back at least 10 years. With the strength of Apple's Java implementation, JDBC is also a popular way to go for application developers. > Also, does anyone know if Apple have plans on documenting their iODBC > a bit better? ODBC in general is a mature technology that is well documented by MS and others. Apple appears to be doing the basics to support iODBC and JDBC, and letting the market decide which will become the dominant technology. That may not sound like much, but just by the fact they made a stand and chose iODBC over competing implementations such as unixODBC has helped to clear up the data access picture a great deal. > Right now I'm having to use MS's ODBC documentation, which while OK, I > would definitely expect Apple's documentation to be better ;o) You're right that Apple's technical documentation is generally better. However, ODBC is a Microsoft technology, and their documentation is pretty good. For the most part, what you'll find on MSDN also applies to iODBC. If you'd like an example project file to help you get going, send me an e-mail offline and I'll be happy to send one to you. Just let me know which compiler and language you'd like to use. Best regards, Jonathan Monroe Actual Technologies - ODBC for OS X http://www.actualtechnologies.com mo...@ac... |