| # |
Jun 13th 2018, 08:58 |
 josbeir |
the whole validation => context is pretty complex, haven't looked at it in great detail |
| # |
Jun 13th 2018, 08:58 |
josbeir |
i'm not sure, thats the problem :) |
| # |
Jun 13th 2018, 08:57 |
josbeir |
for me yes, but dont think it should work like that |
| # |
Jun 13th 2018, 08:56 |
lorenzo |
would the result be desirable to you? |
| # |
Jun 13th 2018, 08:56 |
lorenzo |
what happens if you sacrifice one of the conflicting features? |
| # |
Jun 13th 2018, 08:55 |
lorenzo |
I’m aware of the ticket |
| # |
Jun 13th 2018, 08:53 |
josbeir |
(the issue is in the DocumentContext::error method that doesn't take care of nested paths) |
| # |
Jun 13th 2018, 08:52 |
josbeir |
hope i'm not to cryptic with the description :) |
| # |
Jun 13th 2018, 08:52 |
josbeir |
and i'm not sure how to 'fix' this correctly, that both use cases work correctly |
| # |
Jun 13th 2018, 08:51 |
josbeir |
nested validation rules on the current form context dont work currently, but in test cases they do work when the sub entity has errors, the problem is that nested validation sets the errors of the sub entity on the parent context (or something like that) |
| # |
Jun 13th 2018, 08:50 |
josbeir |
@lorenzo i'm struggling a bit with the formContext and nested validation rules in the ES plugin, maybe you could shed a light |
| # |
Jun 13th 2018, 08:49 |
lorenzo |
please open a ticket about it |
| # |
Jun 13th 2018, 08:49 |
lorenzo |
that’s an interesting side effect |
| # |
Jun 13th 2018, 08:49 |
josbeir |
morning all |
| # |
Jun 13th 2018, 08:49 |
lorenzo |
the newer time class has support for microseconds |
| # |
Jun 13th 2018, 08:48 |
lorenzo |
ah, yes |
| # |
Jun 13th 2018, 08:46 |
rudy1976s |
@lorenzo it seems that setting SQLServer column type from "datetime" to "datetime2" fixed the problem: does the timestamp behavior changes the way it handles data in the last version of cake ? Datetime2 differs from Datetime in several ways , first of all ability to store bigger information in lesser space reading from Microsoft official docs and the date stored in DB is like the following : 2018-06-13 10:40:43.0000000 |
| # |
Jun 13th 2018, 08:28 |
slackebot |
Action: admad put on "Another brick in the wall" |
| # |
Jun 13th 2018, 08:28 |
admad |
i guess it's spelled "laddie" |
| # |
Jun 13th 2018, 08:26 |
admad |
moin, get to work laddy :slightly_smiling_face: |
| # |
Jun 13th 2018, 08:23 |
neon1024 |
Morning |
| # |
Jun 13th 2018, 08:22 |
lorenzo |
so we can fix it |
| # |
Jun 13th 2018, 08:22 |
lorenzo |
try to create a small reproducible example of your problem and open a ticket about it |
| # |
Jun 13th 2018, 07:44 |
rudy1976s |
same of all |
| # |
Jun 13th 2018, 07:44 |
rudy1976s |
same basecode |
| # |
Jun 13th 2018, 07:44 |
rudy1976s |
this problem afflicts only SQLServer while the upgrade does not create issue on mysql server |
| # |
Jun 13th 2018, 07:42 |
rudy1976s |
both in create and edit |
| # |
Jun 13th 2018, 07:41 |
rudy1976s |
and if I put the timestamo behavior off from the table no error |
| # |
Jun 13th 2018, 07:40 |
rudy1976s |
this happened only after update to 3.6.5 |
| # |
Jun 13th 2018, 07:40 |
rudy1976s |
Hi lorenzo |
| # |
Jun 13th 2018, 07:38 |
lorenzo |
or maybe you have a custom getter for the property in the entity |
| # |
Jun 13th 2018, 07:38 |
lorenzo |
Likely because you are setting the field directly in the entity |
| # |
Jun 13th 2018, 07:38 |
lorenzo |
You are saving a string as a date |
| # |
Jun 13th 2018, 07:36 |
rudy1976s |
my sql server column tipe for created and modified is Datetime and all worked before update |
| # |
Jun 13th 2018, 07:35 |
rudy1976s |
a conversion of a nvarchar data type into datetime has generated a value that is outside the range of allowed values |
| # |
Jun 13th 2018, 07:35 |
rudy1976s |
the error in english is |
| # |
Jun 13th 2018, 07:35 |
rudy1976s |
is there any important change to timestamp behavior ? |
| # |
Jun 13th 2018, 07:34 |
rudy1976s |
Error: SQLSTATE[22007]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]La conversione di un tipo di dati nvarchar in datetime ha generato un valore non compreso nell'intervallo dei valori consentiti. |
| # |
Jun 13th 2018, 07:34 |
rudy1976s |
I have updated cake to last version and after that every table with TimeStamp behavior will cause on my SQLServer database the following error |
| # |
Jun 13th 2018, 07:34 |
willem |
on my online server i get this error quite a lot when enabling debugging : `SQLSTATE[HY000]: General error: 11 database disk image is malformed` . Deleting the sqlite file fixes this error, but it will come back eventually. I could not find _why_ this is happening. Anybody? |
| # |
Jun 13th 2018, 07:34 |
rudy1976s |
good mornign to all |