this is about the part of "columns sort on null and sorting case insensitive
that is stored in DBI files. even now at the server level (instead of just the column level)
those DBI files that you have in the developer, are now included in the WAR “as is” so no more repository “column_info” table
So if for example you use this in the server editor:
[attachment=0]server_editor.png[/attachment]
that information doesn’t get into the WAR when you are just using .servoy files (because the .servoy file doesn’t have that)
can you please confirm recap below (so I’m not assuming things that are not written)
Clearly, this change was already part of 2022.9
Exporting a .war file INCLUDING the solution will generate a .war file which holds the table/column information in .dbi files and no longer in a repository.
Exporting a .war file WITHOUT the solution will allow you to import solutions and will still store the table/column information in the repository (also read: an import of the new solution can actually add columns to the DB)
Only when deploying full .war file (including solutions) you will have the ability to configure the behaviour of Servoy when it comes to sorting records.(nulls first/last and/or ignore-case)
jcompagner:
Stuff about those new features are described in the release notes of 2022.09 https://wiki.servoy.com/display/DOCS/2022.09+Whats+new
this is about the part of "columns sort on null and sorting case insensitive
that information doesn’t get into the WAR when you are just using .servoy files (because the .servoy file doesn’t have that)
Thank Johan for letting us know (& your reply to Marc).
I think I might be able to cope with not having that new feature, so will carry on ‘the old way’
For those less comfortable with WAR deployment, Servoy Cloud is probably the best way to go. I haven’t personally used it, but webinars and stuff I’ve seen on it look pretty great.
If you are looking for alternatives and Servoy Cloud doesn’t fit for your situation, we do have automated deployments working with many clients on many different cloud services (AWS, Azure, Google, In house, etc). Its something we do for our consulting customers, but we haven’t “packaged it up” into something that could be offered to other consultants/developers. Its not as fancy and Servoy Cloud, but does work well. Essentially its GitHub actions that build (and optionally deploy) your WAR file based on commit tags or messages, so you control when it happens. If there is enough interest, we’d consider formalizing that into something that could be easily used by others and able to be purchased (or included for those that already purchase our All Products Pack bundle)
sbutler:
If there is enough interest, we’d consider formalizing that into something that could be easily used by others and able to be purchased (or included for those that already purchase our All Products Pack bundle)
Also just to clarify something I read above:
One does NOT need the command-line exporter, unless they want to automate their war file generation. I’m just worried that someone reading this thread would infer that generating a war file is necessarily a complex programming challenge. It is not.
sbutler:
If there is enough interest, we’d consider formalizing that into something that could be easily used by others and able to be purchased (or included for those that already purchase our All Products Pack bundle)
