Because as far as I know, 1.1 amd 1.2 (and then 1.3) are transition
version which will lead eventually to 2.0 which will again (most
probably) be supported for 3+ years.
2008/11/17 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
> Actually it was not me who chose the symfony version to work in.
> It's in
Actually it was not me who chose the symfony version to work in.
It's interesting - why are they going to maintain v1.0 for whole three
years - but 1.1 and 1.2 only for 1 year?
On 17 нояб, 16:45, "Kiril Angov" <[EMAIL PROTECTED]> wrote:
> I am personally using the plugin on Symfony 1.0 and it wor
I am personally using the plugin on Symfony 1.0 and it works just
fine, if you want to stay as close as possible to the symfony library
versions. Why not use Symfony 1.2, btw? It is ready for use and as it
seems you are not working on a production ready project yet. There is
not point to start with
I'm using Propel 1.2, though 1.3 may be installed as plugin, right?
Actually I don't know - does it worth it? Installing Propel 1.3 as
plugin I mean? One advantage I've already seen - are there any others?
On 17 нояб, 16:17, "Kiril Angov" <[EMAIL PROTECTED]> wrote:
> Did you try:
>
> sess_time:
Did you try:
sess_time: { type: datetime, defaultExpr: "NOW()" }
You must be using Propel 1.3 for this to work, though.
2008/11/17 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
> Hi Kirill, look what I found out. When I define session table in
> schema.yml like that:
>
> session:
>sess_id: { typ
Hi Kirill, look what I found out. When I define session table in
schema.yml like that:
session:
sess_id: { type: VARCHAR, size: '40', required: true, default:
'' }
sess_data: { type: LONGVARCHAR, required: false }
sess_time: { type: INTEGER, unsigned:true }
console tells me that I
Hi, Kiril.
Yes, I define this table in schema.yml. So I just need to know how to
define by default the current time. I've never heard about defaultExpr
attribute so I searched - but haven't found almost anything, the first
result was this page. Please, tell me if you know how to do it!
P.S. Sorr
Are you defining this table in your schema.yml or it is pre-created
and you are just using it for the session storage. Give some more
details and I am sure we will be able to help... and save one life :)
FYI, the default attribute in schema isn't meant to support SQL
functions like CURRENT_TIME.