VDN - Primary Key Constraint & Boolean Fields Question

[Johnny Harris]

Ivan,

It appears that I can update a record as long as I don’t try to update the is_void (BOOLEAN) field.

If I remove that field from my sql query, I can update the record all I want. As soon I add it back to the query string... I get the error.

I also tried updating the record using the cursor.UpdateRecord method but get the error code 353536. The error message associated
with the error code is blank, so I’m not sure what the error code means.

Best Regards,
Johnny Harris


From: Johnny Harris 
Sent: Sunday, March 30, 2014 6:53 AM
To: Valentina Developers 
Subject: Re: VDN - Primary Key Constraint & Boolean Fields Question

Hello Ivan,

Yes, the pk field is causing the error I believe. It is the primary key field for the table.
I never try to change it. I only reference it for updates, deletions and lookups. I’m assuming this
is the field that is causing the error, but I’m not sure. Sometimes I can update a record with no 
problem. Other times trying to update a record throws the exception, but I’ve not found a definite
reason why. I’m looking through my code some more this morning. I will reply back if I find something
in my code causing the issue.

I was just curious about the BOOLEAN type. It’s fine indexed if there’s no cost. Not a problem.

Best Regards,
Johnny Harris

From: Ivan Smahin 
Sent: Sunday, March 30, 2014 3:49 AM
To: Valentina Developers 
Subject: Re: VDN - Primary Key Constraint & Boolean Fields Question


On Mar 30, 2014, at 5:29 AM, Johnny Harris <johnny at southshore.com> wrote:


  Greeting Everyone,

  1. I’m getting an error when I try to update a table record using SQL.

  Error: Primary key constraint violation occurred, table name = “support_payments”, constraint name = “PK_support_payments_pk”.

  I don’t get this error every time I try to update a record. Just occasionally. I’m not trying to update the primary key field, so I’m not really
  sure why I’m receiving this error.



I will check this once more. But we are speaking about this field pk SERIAL64 PRIMARY KEY ?





  2. When I create a table in code, the fields I define as BOOLEAN are Indexed by default. I don’t need the fields indexed.


Actually, "automatic" indexed flag for boolean field costs nothing to you due to the specific implementation. 
Why do you need to have it not-indexed?


-- 

Best regards,
Ivan Smahin
Senior Software Engineer
Paradigma Software, Inc
Valentina - The Ultra-Fast Database
http://www.valentina-db.com



--------------------------------------------------------------------------------
_______________________________________________
Valentina mailing list
Valentina at lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina



--------------------------------------------------------------------------------
_______________________________________________
Valentina mailing list
Valentina at lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macserve.net/pipermail/valentina/attachments/20140330/3652b828/attachment-0001.html>