Locking -- and how to share update code as open source

Phil Phil at pgpotter.co.uk
Wed Dec 14 03:23:39 EST 2016

Hi Bas, Doug,

Yes your probably true, my solution is at a basic level, but good enough 
for many environments, I don't recall how much more you would get with 
an Omnis datafile solution though.

When you need to go that step more, with indexes and referential 
integrity, and code that probably goes across multiple SQL data types...
I'm sure it would not take that much more to add that functionality?

I'm with you Doug, I'd be happy to contribute to the open source pot...
For sure I'd learn from others, and at the end of the day, we all sell a 
solution as a whole, not bits of code...
So if we can grab a few building blocks to make that a quicker process, 
surely that is good for all?


On 14/12/2016 01:17, Bastiaan Olij wrote:
> Hey Doug,
> I'd welcome that future and will surely become a contributor.  Well you
> know me, there are plenty of little libraries I've made over the years
> already floating around there in the public domain, what is lacking is a
> central point where people can find what I and others have made. Besides
> the VCS aspect that allows us to collaborate I also think there should
> be a place to store stable copies people can just grab and run with. I'd
> love to see an asset store within the developer hub in Studio where
> people can upload and share libraries they've created for the community
> (I'm using something similar in other programs I use).
> And indeed, I'm sure there are many different solution out there already
> for this particular issue as each and everyone who's gone to SQL has had
> to deal with this in some way, shape or form. It'll be interesting too
> see what will come to the table when we have an active way to work
> together and build a community solution for this, IMHO critical piece of
> the puzzle for any Omnis developer wanting to make the move to SQL.
> Cheers,
> Bas
> On 14/12/2016 10:51 AM, Doug Easterbrook wrote:
>> hi all:
>> ok, so this is being sidetracked a little by the notion that its pretty easy to add code to an omnis program that will update a SQL database with schema changes on the fly — much like the check data file concept.
>> for what its worth, we do the same thing to our databases — for a long time all the code was in one method that added fields and backfilled data as required — with the nice benefit of consistency though a data dictionary that we put in our application.
>> I’m sure that the three of us are not the only ones who have a mechanism in place to accomplish this…. and I’m sure that any solution we’ve done is probably bested by others out there in the community.
>> It seems to me that this concept is a worthwhile bit of code that could be contributed to the open source world for the over all benefit of omnis ….
>> So, I’m making a point here to the broader world about the notion of open source to solve problems.  It is something that was talked about at euromnis fairly extensively — but the mechanism to share code easily is currently a little lacking.
>> if you read the proposed release notes for Studio 8.1 presented in Boston, one of the features on the slide was ‘ability to export/import libraries as json’.      Most of you know that we are a big proponent of open source and sharing — and so this upcoming feature has tremendous and fantastic implications …
>> The goal is to be able to use git repositories for the libraries and let all of us share some core features ….     there are a few of us hoping to play with this as soon as it is available……
>> just wanted to say that an easy-update of a sql database could be a really good sample project for open source.
>> Doug Easterbrook
>> Arts Management Systems Ltd.
>> mailto:doug at artsman.com
>> http://www.artsman.com
>> Phone (403) 650-1978
>> bas said:…..
>>> On Dec 13, 2016, at 4:03 PM, Bastiaan Olij <bastiaan at basenlily.me> wrote:
>>> As I said, I've long wanted to redo this logic we've developed into a
>>> library that can be used by anyone within the community so they do not
>>> have to build this. It was one of the reasons I did my session at
>>> EurOmnis last year. I just need to find the time to actually do it.
>> Phil said:
>>> We have routines on startup check the schemas in our application,
>>> against, in our case, a postgresql server, and update the server if
>>> there are any required changes...
>>> _____________________________________________________________
>>> Manage your list subscriptions at http://lists.omnis-dev.com


P G Potter, 11 Regency Court, Mickle Trafford, Chester, UK.

This message is confidential and intended for the use only of the person 
to whom it is addressed. If you are not the intended recipient you are 
strictly prohibited from reading, disseminating, copying, printing, 
re-transmitting or using this message or its contents in any way. 
Opinions, conclusions and other information expressed in this message 
are not given or authorised by the Company unless otherwise indicated by 
an authorised representative independent of this message. The Company 
does not accept liability for any data corruption, interception or 
amendment to any e-mail or the consequences thereof. Emails addressed to 
individuals may not necessarily be read by that person unless they are 
in the office.

More information about the omnisdev-en mailing list