Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.8.8/8.7.5) with ESMTP id LAA05235 for ; Thu, 9 Jul 1998 11:40:50 -0400 (EDT) Received: from insightdist.com (nobody@localhost) by u1.abs.net (8.9.0/8.9.0) with UUCP id LAA00732 for pgsql-interfaces@postgreSQL.org; Thu, 9 Jul 1998 11:31:18 -0400 (EDT) X-Authentication-Warning: u1.abs.net: nobody set sender to insightdist.com!byronn using -f Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA30236; Thu, 9 Jul 1998 11:22:55 -0400 Received: from byronn by ceodev (AIX 4.1/UCB 5.64/4.03) id AA52926; Thu, 9 Jul 1998 11:22:54 -0400 Message-Id: <35A4E004.141DD279@insightdist.com> Date: Thu, 09 Jul 1998 11:21:40 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: Giuseppe Tanzilli Cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Memo field in MS Access References: <35A475E6.D326BAC6@fr.flashnet.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Giuseppe Tanzilli wrote: > Hi, > I was porting an Access database to PostgreSQL and I found a > problem. > I had ~12K memo text field in Access, I can't port this to pgsql. > I do not need index, compare on this field. > > There is a way to map a field as a large object ? > Currently, the odbc driver only allows for SQL_LONGVARBINARY to be mapped to a large object, and that is because we have a special "lo" data type that we create in Postgres. (See our FAQ on our website for how to do this) For your case, we would also need to create an "lo_text" data type that would then be mapped to SQL_LONGVARCHAR by the driver. Also, we would need an option to go the other way because currently, SQL_LONGVARCHAR is mapped to a postgres 'text' type. Most users are happy with this mapping so we would need an option. I could add it to my TODO list but if you need it only for one time to import the data, I could just send you a modified version that maps it the way you want. Byron