• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: PostgreSQL vs MySQL for Blobs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PostgreSQL vs MySQL for Blobs


  • Subject: Re: PostgreSQL vs MySQL for Blobs
  • From: Rico Landefeld <email@hidden>
  • Date: Mon, 20 Feb 2006 17:58:07 +0100

Loren Cahlander schrieb:

I am creating a WebObjects application that will have at least three tables containing blobs.  Two containing UniCode text and one containing binary data.  My database preference is PostgreSQL, but it seems that MySQL has an easier to understand implementation of large objects.

If I use PostgreSQL, then is there any special handling of the large objects that I have to do in the EOModel?

Thanks,
Loren


hi,

i'm using PostgreSQL 8.1. for image data i'm using the "bytea" database
datatype mapped to NSData and for text blobs i'm using "text" mapped to
NSString. it works without problems.

rico


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: PostgreSQL vs MySQL for Blobs
      • From: Loren Cahlander <email@hidden>
References: 
 >PostgreSQL vs MySQL for Blobs (From: Loren Cahlander <email@hidden>)

  • Prev by Date: PostgreSQL vs MySQL for Blobs
  • Next by Date: Re: Most efficient character parsing.
  • Previous by thread: PostgreSQL vs MySQL for Blobs
  • Next by thread: Re: PostgreSQL vs MySQL for Blobs
  • Index(es):
    • Date
    • Thread