Am Dienstag 08 Januar 2008 17:31 schrieb Tobias Schlitt:
> Hi!
>
> On 01/08/2008 10:43 AM Thomas Koch wrote:
> > I know you'll hate me, but I've got another 2cents. ;-)
> >
> > I set up a db with a timestamp column (since DatabaseSchema supports it)
> > and wanted to use it in PO with the new date
Hi!
On 01/08/2008 10:43 AM Thomas Koch wrote:
> I know you'll hate me, but I've got another 2cents. ;-)
>
> I set up a db with a timestamp column (since DatabaseSchema supports it) and
> wanted to use it in PO with the new date converter. Unfortunately for me the
> converter accepts only time
Before I upgraded I had an email come in from one of those carriers
I've had problems with. The image was parsed and the header looked
like this:
Content-Location:pic010808_1.jpg
So I'm not sure if that is my problem.. But I upgraded and I report
back soon. Thanks again.
Dave
On Jan 8,
On Jan 8, 2008, at 4:34 AM, Alexandru Stanoi wrote:
> Dave Fischetti wrote:
>> On Jan 7, 2008, at 10:14 AM, Alexandru Stanoi wrote:
>>> Dave Fischetti wrote:
I have all mail coming in and being parsed also redirected to
another email account so I see everything that comes in as I
>
Hi Toby,
I know you'll hate me, but I've got another 2cents. ;-)
I set up a db with a timestamp column (since DatabaseSchema supports it) and
wanted to use it in PO with the new date converter. Unfortunately for me the
converter accepts only time values as integer timestamps, but MySQL returns
Dave Fischetti wrote:
> On Jan 7, 2008, at 10:14 AM, Alexandru Stanoi wrote:
>
>> Dave Fischetti wrote:
>>> I have all mail coming in and being parsed also redirected to
>>> another email account so I see everything that comes in as I test
>>> (since the parsed deletes things immediately). It
