On Mon, Sep 24, 2012 at 10:05 AM, Jeroen Vermeulen <[email protected]> wrote: > On 2012-09-22 17:15, Gavin Panella wrote: >> >> On 21 September 2012 06:30, Jeroen Vermeulen <[email protected]> wrote: >>> >>> Django gets in the way. I forget the details but basically, we found no >>> quick way to make use of bytea fields in django. Right now we base64 >>> into >>> text fields. :( >> >> >> Are we? As far as I can tell we're using Django's FileSystemStorage >> (see maasserver.models.filestorage) to save files to disk, not into >> the database; we store only the filename in the database. For small >> files I think base64 into text fields in the database will be fine for >> now, and a step up from using local disk directly. > > > We do both, in different places. But when it comes to storing binary data > in the database itself, as you were describing, we base64 into text fields > because we couldn't get bytea to work.
Do you recall the problem with bytea btw? The SSO systems needed to set 'bytea_output=escape' in postgresql.conf (or in the session, or with ALTER DATABASE) to get bytea fields working with Django. -- Stuart Bishop <[email protected]> -- Mailing list: https://launchpad.net/~maas-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~maas-devel More help : https://help.launchpad.net/ListHelp
