Is there a way of deleting old versions from the repository. When I try, I get a message that only the latest version can be deleted 
I have 80 releases for some of my modules.
I would also like to have a feature that would allow us to “flatten” a solution. Something like “Delete old releases”…
Nice FEATURE REQUEST…
It’s not really a “bug.” Here’s what I do: export my latest rev, backup the database, and then delete the solution and re-import the solution. Done. I have 1 release.
bcusick:
Nice FEATURE REQUEST…It’s not really a “bug.” Here’s what I do: export my latest rev, backup the database, and then delete the solution and re-import the solution. Done. I have 1 release.
The heading is “Issues and Bugs”, so this is an important issue.
I’m working on 2 large projects, unfortunately they both refuse to import into version 3.0 – and they go back a long time - to version 1.2.
One complains about some value being too long for ‘character varying 50’ – I have searched all fields of that type in the repository and have no values even approaching that length.
The other one complains about some XML problem…
So to keep the wheels spinning and move to 3.0, I have had to dump and restore the repository database rather than import to move between servers… it works but does not solve the import problem.
We have discovered this in the last 3 days and not reported it yet.
What is the best way to report this to the dev team?
The best way to report ‘Issues & Bugs’ directly to the dev team, is by using the Support System Servoy - Error
HTH
I have sent off 2 cases. They both give the same error now:
com.servoy.j2db.persistence.RepositoryException: org.xml.sax.SAXException: Unexpected start tag 'db_sequence_name'
Thanks for reporting, this was a bug. I fixed it and the fix will be in 3.0.1. Your old .servoy files will then import ok.
Great. That was quick 
In the midst of a 2.2.7 to 3.1.4 upgrade, and realized this would be a great feature…why?
Bob’s method is good EXCEPT for the fact that you cannot export and re-import a solution with all the users and groups in with the same servoy repository pk’s. If you’ve ever used servoy user id’s as auto-enter fields, then its a hefty SQL update through all tables.
We did notice 3.1.4 has a new id column for users - assume this is intended to alleviate this to some degree?
Servoy support reponded with the suggestion to upgrade in place…which is fine, but now we’re waiting for 300,000 rows on some of the servoy_element and servoy_releases tables for back ups and backups of backups (can’t be too sure! 
) and backups continue to grow.
Also, can you even REVERT to a prior release if it was imported under previous version?
So, with nearly 80 revisions on two solutions, the repository is getting rather obese (no problems yet, but lean is mean).
We’re not able to do a fresh repository as we still are unable to figure out how to import users / groups and security settings so that servoy user id’s all match up with what they were in the original server.
So, an IN PLACE flatten of the repository would be nice.
OR a way to perfectly copy user/group/security information EXACTLY (preserving servoy’s pk’s) would suffice, too in our case
Nolan M.
FSCI
Hi,
did you try an import/export? Try it into a new repository first and take along the user information. Servoy has been changed so that the javascript functions to get the user ids return the UID field instead of the ID field now, and by default the UID fields were filled with the ID. Thus unless you use custom queries and query for the IDs, it should actually work.
Tried originally to export from 2.2.7 and import into a clean 3.1.4 install. This did NOT work as security settings, users and groups were imported, BUT they had different ID’s - so, all of the AUTO-ENTERED fields that put servoy user id’s in them were no longer valid.
I have NOT tried a 3.1.4 export – > 3.1.4 import yet.
I will when I have time to satisfy my curiousity and see if the behavior has changed - and yes, I did see the UUID vs. ID change when moving to 3.1.4