for use in (and other places where we generate passwords)
branches/1.3/sql/upgrade/1.2-1.3.sql
CREATE OR REPLACE FUNCTION random_string(INTEGER)
RETURNS TEXT AS
$BODY$
SELECT array_to_string(
ARRAY (
SELECT substring(
'0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwx
I just added a script in trunk to rebuild the .pot and just committed an
updated .pot.
Long-run we need to fix these variable interpolation issues in the old code.
I fixed one.
Best Wishes,
Chris Travers
On Thu, Dec 20, 2012 at 9:52 AM, Pongrácz István
wrote:
>
> Hi,
>
> The solution:
>
On Mon, Dec 24, 2012 at 9:36 PM, ario wrote:
> Ok, as I'm intending to use VMs for lsmb and to freshly make new ones
> for every upgrade, I won't need LTS OSs like Ubuntu or CentOS.
> So I better decide to go with Fedora for now.
>
FWIW I think a simple rpmbuild --rebuild on the .src.rpm is suf
Ok, as I'm intending to use VMs for lsmb and to freshly make new ones
for every upgrade, I won't need LTS OSs like Ubuntu or CentOS.
So I better decide to go with Fedora for now.
thanks
On Sat, 2012-12-22 at 14:54 -0800, Chris Travers wrote:
> The RPMs are built on Fedora, of a more recent ver
Hi John;
It occurs to me that if we go with Erik's suggestion we could maintain this
as a separate feature branch for 1.5 and expect to fold it into standard
for 1.6. This would avoid skipping required PostgreSQL versions (since our
release is starting go move towards something more similar to th
Hi,
On 09/17/2012 02:44 AM, Chris Travers wrote:
> Hi all;
>
> I have been thinking about the way we handle customizations in old
> code vs new code where new fields need to be added. Currently adding
> these for old code is pretty easy, but adding them for new code is a
> little more problema
