On Tue, May 27, 2008 at 4:18 AM, Mark Neely <[EMAIL PROTECTED]> wrote:
> I've already shortlisted potential CMS systems (including several open-
> source options, such as Drupal and Joomla).
[snip...]
> I am looking for examples of open-source CRM (or similar platforms)
> used for this kind of pr
On 8/21/07, Guy Rouillier <[EMAIL PROTECTED]> wrote:
> Well, I can't find a way to set a variable associated with a connection,
> so probably the easiest thing to do is to add an "updated_by" column to
> your regular table (i.e., the non-history version.) Then just include
> the userid from your w
On 8/21/07, Guy Rouillier <[EMAIL PROTECTED]> wrote:
> Well, you haven't told us much about your webapp. Are you using
> connection pooling? If so, then you'll need to provide the webapp
> userid as an additional parameter to your database updates. If you are
> not using connection pooling, such
Hi,
I want to save history for a few tables using triggers on update and
creation. What's the best approach to do this in a webapp environment
where I want to save which webapp user that is doing the change, not
the postgresql user?
--
regards,
Robin
---(
On 8/19/07, Michael Glaesemann <[EMAIL PROTECTED]> wrote:
> As you mention, you could use a trigger instead of explicitly setting
> updated_at to DEFAULT, which might be more convenient because you
> don't need remember to set the updated_at column explicitly on update.
>
> Whether or not this info
Hi,
When I started with MySQL I exploited their "bug" with timestamp
fields and always had a entered and updated field on my tables.
My question, is this interesting information enough to save on the
table itself? If so, I guess this could easily be solved with a
trigger, however, should one inst
