*** dimas has joined #gnuenterprise
*** titopbs has quit IRC
*** bluesbaron_ has joined #gnuenterprise
*** bluesbaron_ has left #gnuenterprise
*** sjc has joined #gnuenterprise
*** sjc has quit IRC
*** lekma has joined #gnuenterprise
<lekma> hi
<lekma> DB000: In file(s) '1010_accounts_Accounts.gcd':
<lekma> DB000: Property 'accounts_accounts.accounts_accounttype' cannot be added to existing class with 'NOT NULL' constraint
<lekma> in gnue-readgcd
<lekma> it's quite new to me that one cannot add a not null property
<lekma> is threre a reason why?
*** tiredbones has joined #gnuenterprise
*** mnemoc_ has joined #gnuenterprise
*** mnemoc has quit IRC
*** havoc has quit IRC
*** havoc has joined #gnuenterprise
*** titopbs has joined #gnuenterprise
*** johannesV has joined #gnuenterprise
<johannesV> lekma, are you there ?
<johannesV> you cannot add a 'not-null'-property to an existing class for a simple reason:
<johannesV> if the table has already records in it, they would all violate the not-null constraint introduced by the new property ...
<johannesV> because they don't have a value yet
<johannesV> usually the backend-database raises an error if you try something like this
<johannesV> there's one exception to this: some databases might allow such an "alter table" if there's no data in the table at that time
<lekma> could readgcd test for existing records?
<johannesV> lekma, schema-creation is not done by gnue-readgcd directly but by gnue-common's schema-creation
<johannesV> gnue-readgcd has no clue about existing relations or properties though
<lekma> oh ok
<johannesV> it cannot check for this. if there should be a solution it must be handled by gnue-common
<johannesV> but i think this isn't really usefull, cause it's not given that all backends support such an alter table
<johannesV> that's why we've decided to catch such a situation directly in gnue-readgcd
<johannesV> we could do a check for existing records and if there aren't any gnue-readgcd could decide not to raise an exception, hoping the backend can create the schema
<johannesV> the drawback would be that for a backend which can't handle this, a database-error is sent to the user (which is usually quite cryptic)
*** xet7 has joined #gnuenterprise
*** titopbs has quit IRC
<lekma> johannesV: i work around the issue earlier, that was merely a suggestion i was making, thx anyway for the explanation
*** xet7 has quit IRC
*** holycow has joined #gnuenterprise
*** SachaS has joined #gnuenterprise
*** alandd has joined #gnuenterprise
<alandd> dere1: That you?
<alandd> anyone: internal server error attempting to use the search engine on gnue.org
<alandd> just thought someone should know if they don't already.
<alandd> brb
*** SachaS has quit IRC
*** johannesV has quit IRC
<alandd> b
*** sjc has joined #gnuenterprise
<alandd> gotta bail for a bit.  I'll be back.
*** alandd has quit IRC
*** alandd has joined #gnuenterprise
<alandd> back.  What'd I miss?
*** tiredbones has quit IRC
*** titopbs has joined #gnuenterprise
*** titopbs has quit IRC
*** titopbs has joined #gnuenterprise
*** titopbs has quit IRC
*** lekma has quit IRC
*** titopbs has joined #gnuenterprise
*** titopbs has quit IRC
<alandd> dere1: are you here?
*** titopbs has joined #gnuenterprise
*** titopbs has quit IRC
*** tiredbones has joined #gnuenterprise
*** titopbs has joined #gnuenterprise
*** titopbs has joined #gnuenterprise
*** titopbs has quit IRC
*** titopbs has joined #gnuenterprise
*** titopbs has quit IRC
*** titopbs has joined #gnuenterprise
*** titopbs has quit IRC
*** titopbs has joined #gnuenterprise
*** titopbs has quit IRC
<mnemoc> uhm
*** titopbs has joined #gnuenterprise
*** holycow has quit IRC
*** titopbs has quit IRC
<alandd> titopbs made 6 minutes that time!
* alandd is bored...
*** jcater has joined #gnuenterprise
*** alandd has quit IRC
*** jcater has quit IRC
*** abl has joined #gnuenterprise
*** holycow has joined #gnuenterprise
*** sjc has quit IRC
*** dcmwai has joined #gnuenterprise
*** tiredbones has quit IRC