Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Field imagepos on #__contact_details

Date: Tue, 17 Apr 2012 16:48:48 -0700 (PDT)
From: brian teeman <jooml...@googlemail.com>
To: joomla-dev-cms@googlegroups.com
Message-ID: <5337237.397.1334706528031.JavaMail.geo-discussion-forums@vbyz30>
In-Reply-To: <12989180.665.1334706449994.JavaMail.geo-discussion-forums@yncc41>
References: <CAHtW0Z9RZFkZxaqPJc1rDXdEReG5n5gP0D6R01_6k2L49iTjeA@mail.gmail.com>
 <CABYB9+DyB4Sw=01LYYZQrazCRQnrQDaHwLX_Si0UcTCDYz2s5g@mail.gmail.com>
 <CAHtW0Z-M4GEQ+p0G3NXJZ=9byhASFKQ0DP9TRCf4jn+13VYc4A@mail.gmail.com>
 <28719055.5.1334561512022.JavaMail.geo-discussion-forums@vbda10>
 <85ECEA49-1CDE-44AF-A89F-C16FA5943CED@gmail.com>
 <CABYB9+CPvuqjpb2zfadHKpmKmbbjyFF9zboQfY2ihcxd02NSgA@mail.gmail.com>
 <889C7E54-9824-44E4-8F70-5C89B4134A1F@gmail.com>
 <773128.40.1334619543971.JavaMail.geo-discussion-forums@vbbfr18>
 <CAHtW0Z9mCB6n9Q6Cebf8SGzM70SOQGpbYYqj7R3iHK3Xx=tp8Q@mail.gmail.com>
 <12989180.665.1334706449994.JavaMail.geo-discussion-forums@yncc41>
Subject: Re: [jcms] Field imagepos on #__contact_details
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_395_17959187.1334706528029"

------=_Part_395_17959187.1334706528029
Content-Type: multipart/alternative; 
	boundary="----=_Part_396_17950451.1334706528029"

------=_Part_396_17950451.1334706528029
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit



On Wednesday, 18 April 2012 00:47:29 UTC+1, elin wrote:
>
> Can you just change the definition to something that doesn't cause 
> problems?  No one using postgres is going to have any old data anyway.


But some extensions might be 

 

> For deprecated fields we'd usually add the word deprecated to the first 
> row of the table.
>
> Elin
>
> On Tuesday, April 17, 2012 4:02:50 PM UTC-4, Gabriele Pongelli wrote:
>>
>> How is it possible to deprecate this field ?
>> Have I to cut it from my Postgresql branch?
>>
>> Eng. Gabriele Pongelli
>>
>
------=_Part_396_17950451.1334706528029
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Wednesday, 18 April 2012 00:47:29 UTC+1, elin  wrote:<blockquote=
 class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1=
px #ccc solid;padding-left: 1ex;">Can you just change the definition to som=
ething that doesn't cause problems? &nbsp;No one using postgres is going to=
 have any old data anyway.</blockquote><div><br></div><div>But some extensi=
ons might be&nbsp;</div><div><br></div><div>&nbsp;</div><blockquote class=
=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #cc=
c solid;padding-left: 1ex;"><div>For deprecated fields we'd usually add the=
 word deprecated to the first row of the table.</div><div><br></div><div>El=
in<br><br>On Tuesday, April 17, 2012 4:02:50 PM UTC-4, Gabriele Pongelli wr=
ote:<blockquote class=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;b=
order-left:1px #ccc solid;padding-left:1ex">How is it possible to deprecate=
 this field ?<br>Have I to cut it from my Postgresql branch?<p>Eng. Gabriel=
e Pongelli<br></p></blockquote></div></blockquote>
------=_Part_396_17950451.1334706528029--

------=_Part_395_17959187.1334706528029--