1) Timestamp attribute
Using function AS_TIMESTAMP to set a specific initial value to a timestamp attribute doesn't work.
The log says: "Value was not changed because it was equal to the old value: null"
2) Date format MMMM (month name)
Defining a date attribute with format dd MMMM YYYY brings Error: invalid date format.
I'm sending a bsv to support.
Initializing Timestamp attribute // Date format MMMM
Initializing Timestamp attribute // Date format MMMM
Build 1246 - Windows/Mysql
pixerp,
#1 -- use function: CURRENT_TIMESTAMP
#2 -- use: dd MMMM yyyy
FYI -- a previous post pointed to this:
http://java.sun.com/j2se/1.4.2/docs/api ... ormat.html
#1 -- use function: CURRENT_TIMESTAMP
#2 -- use: dd MMMM yyyy
FYI -- a previous post pointed to this:
http://java.sun.com/j2se/1.4.2/docs/api ... ormat.html
Tom - V8.8 build 3137 - MySql / PostGres
Hi Tom,
sorry, you are right with the solution, actually i post something else,
my problem is niether #1 nor #2.
with the function and format it is ok.
but like when we create a new attribute with timestamp or date type, we not able to format in this way MM YYYY.
As this is required when we have to enter only month and year.
Did you got it what i mean.
Thanks
sorry, you are right with the solution, actually i post something else,
my problem is niether #1 nor #2.
with the function and format it is ok.
but like when we create a new attribute with timestamp or date type, we not able to format in this way MM YYYY.
As this is required when we have to enter only month and year.
Did you got it what i mean.
Thanks
From,
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Timestamp
Setting the attribute initial value with CURRENT_TIMESTAMP was ok.
The problem was setting an initial value sometime in the past. I tried to define a BO rule like "If BO1.myTimestamp IS UNDEFINED Then BO1.myTimestamp=AS_TIMESTAMP('2000-01-01 00:00','YYYY-MM-dd HH:mm')" or "If BO1 IS NEW Then ..."
NOW I notice the small caps for yyyy as per Tom's post. AND THIS WORKS.
Date with month name
I checked the format and it's dd MMMM yyyy indeed. The error is a screen popup "Attribute has invalid format".
Seems like a bug ? In my test bsv I'm not using any locale.
Thanks
Setting the attribute initial value with CURRENT_TIMESTAMP was ok.
The problem was setting an initial value sometime in the past. I tried to define a BO rule like "If BO1.myTimestamp IS UNDEFINED Then BO1.myTimestamp=AS_TIMESTAMP('2000-01-01 00:00','YYYY-MM-dd HH:mm')" or "If BO1 IS NEW Then ..."
NOW I notice the small caps for yyyy as per Tom's post. AND THIS WORKS.
Date with month name
I checked the format and it's dd MMMM yyyy indeed. The error is a screen popup "Attribute has invalid format".
Seems like a bug ? In my test bsv I'm not using any locale.
Thanks
Build 1246 - Windows/Mysql