pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Memo field in MS Access
2+ messages / 2 participants
[nested] [flat]

* Memo field in MS Access
@ 1998-07-09 07:48  Giuseppe Tanzilli <g.tanzilli@fr.flashnet.it>
  0 siblings, 1 reply; 2+ messages in thread

From: Giuseppe Tanzilli @ 1998-07-09 07:48 UTC (permalink / raw)
  To: pgsql-interfaces

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 ?

Thanks in advance

I do not read the list, so I will apreciate a direct mail.
bye


-----------------------------------------------------------------
Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
mailto: g.tanzilli@flashnet.it  Sede di Frosinone
Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
Tel: +39-775-830012             http://www.flashnet.it
Fax: +39-775-201321             EUnet Business Partner
http://www.eurolink.it          AIIP and ANFOV associated
PGP Key: finger giuseppe@king.fr.flashnet.it
-----------------------------------------------------------------





^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: [INTERFACES] Memo field in MS Access
@ 1998-07-09 15:21  Byron Nikolaidis <byronn@insightdist.com>
  parent: Giuseppe Tanzilli <g.tanzilli@fr.flashnet.it>
  0 siblings, 0 replies; 2+ messages in thread

From: Byron Nikolaidis @ 1998-07-09 15:21 UTC (permalink / raw)
  To: Giuseppe Tanzilli <g.tanzilli@fr.flashnet.it>; +Cc: pgsql-interfaces



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




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~1998-07-09 15:21 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-07-09 07:48 Memo field in MS Access Giuseppe Tanzilli <g.tanzilli@fr.flashnet.it>
1998-07-09 15:21 ` Byron Nikolaidis <byronn@insightdist.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox