pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Lynna Landstreet <lynna@gallery44.org>
To: pgsql-php@postgresql.org
Subject: Re: Sessions and serializing (was: Checking data inserted
Date: Wed, 19 May 2004 17:15:19 -0400
Message-ID: <BCD146A7.12C2%lynna@gallery44.org> (raw)
In-Reply-To: <000301c43879$fb8ff390$0d00a8c0@chris>

Hmmm, so my entire idea for how to do this appears to have been unsound.
Well, better to find that out sooner than later! Thanks to everyone who
replied.

But I have a few questions:

on 5/12/04 7:36 PM, Chris at chris@interspire.com wrote:

> You could serialize up the data in sessions and then use that data
> before adding it to the database.
> See http://www.php.net/serialize and http://www.php.net/unserialize and
> http://www.php.net/session

OK, so if I understand this correctly, the serialize function can take
something like a big associative array containing all the data I want to be
able to write into the database and condense it into a single object that
can be passed via a hidden form field or something to that effect, correct?
Or the data can be put into the session array using $_SESSION, and then
passed by using a $session_id in the page URL?

But according to one of the user comments in the manual I have to use
addslashes() and stripslashes() if I want to be able to put the data into
the database after unserializing it - is that right?

Also, what about character encoding? My database and my web pages are utf-8
because of the presence of special characters in some of the artists and
names and image and exhibition titles (it's a Canadian gallery, so there are
a lot of French artists). Will serializing the array containing the data
affect that in any way?

Sorry if I'm being a pest - the whole session thing is new to me and I want
to make sure I understand it correctly.

Thanks,

Lynna

-- 
Resource Centre Database Coordinator
Gallery 44
www.gallery44.org




view thread (5+ messages)  latest in thread

Message-ID: <BCD146A7.12C2%lynna@gallery44.org>
Permalink:  ../BCD146A7.12C2%25lynna@gallery44.org/
Also on:    postgresql.org/message-id/BCD146A7.12C2%lynna@gallery44.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: lynna@gallery44.org
  Subject: Re: Sessions and serializing (was: Checking data inserted
  In-Reply-To: <BCD146A7.12C2%lynna@gallery44.org>
  References: <000301c43879$fb8ff390$0d00a8c0@chris> <BCD146A7.12C2%lynna@gallery44.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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