My goodness, VARBINARY sucks so much!
When I wan to run some SELECT
statements on some tables, I always get a SQL query like SELECT *, HEX(`column`) AS `column` FROM `table` WHERE `other` LIKE UNHEX('%foo%')
in tools like #Adminer (a PHP-based web-frontend I usually use to administrate my database server). This causes it that zero records are being found and the culprit here is the wrong/excessive use of VARBINARY
instead of VARCHAR
(string variable character length) and a proper collation like utf8_general_ci
for all tables.
I don't know why you e.g. want to have non-alpha-numerical characters in URLs or keys?! Why on good Earth that? I think a #RFC states that such characters needs to be URL-encoded with %HEX-CODE
to avoid interference with not so tolerative systems. For example, I sometimes like to know how many contacts my node knows for a specific domain, so I usually choose LIKE %%
and enter the domain name to look for. It worked always flawless before but since VARBINARY
is in place, I can no longer find records.
Very sad to see such development.
CSS class' "icon" property "height" causing distance beween two lines in profile views
The said #CSS class .icon
has a property height: 48px
which with current HTML structure causes a distance between two lines when I view a remote profile (view: /contact/X
or a post (view: /display/X
):
I'm sure, removing height
from the said CSS class won't fix it in the long run but maybe checking the HTML/div structure would.
Friendica Support reshared this.
Null-safe invocation of Enum.compareTo()?
I look for an utilities class or self-implementation to invoke Enum.compareTo()
in a null-safe manner.
Does anyone know such a class or how to implement it? I have a few enumerations written here and I COULD write one for each one. But I guess there might be a more intelligent and flexible way to do this.
The background here is that I have a public default constructor for the #JPA here and an other constructor that beside some other class fields sets this enumeration. Still I need to compare both instances ("empty" one and one with set values) in a null-safe manner. If I try to implement it without the null-check, it throws the all-famous #NPE at me and a unit-test fails.
PS: Is there a #Java group/forum like !java
available somewhere?
Enum.compareTo()
by implementing a static method accepting Enum<?>
as types) and then checking both on equality (==
) and null
each. If none of them is null
, the method Enum.compareTo()
can be safely invoked.
Blackbird reshared this.
Sylvia J likes this.
Roland Häder🇩🇪
in reply to Roland Häder🇩🇪 • •$ git blame view/global.css
that the commit47ad922f9a1827e0f80f9ad473d821915abf4d60
introduced this change.Friendica Support reshared this.
Roland Häder🇩🇪
Unknown parent • •view/global.css
, was somit fuer alle Designs gilt.Friendica Support reshared this.
Roland Häder🇩🇪
Unknown parent • •Friendica Support reshared this.