AirNav RadarBox
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 


Author Topic: A380 Database Info  (Read 11493 times)

0 Members and 1 Guest are viewing this topic.

Really

  • New Member
  • *
  • Posts: 41
Re: A380 Database Info
« Reply #15 on: March 19, 2008, 05:45:07 PM »
It is possible to add an empty character (space) to the manual entry
and if that happens at least for the eye there are 2 identical entry's
but there hex values will be different.....

You shouldn't be able to do that either.  Again, that's one of the changes I got Airnav to make to the NavData tables during beta testing of v1.4 - in fact, I made the changes for them myself.  They were originally plain text fields, but I got Airnav to change them, and the MS field is varchar(6), so can only have 6 characters.



I don't understand how you could add a space on the end of a 6 character hexcode field?

SQLite does not support the VARCHAR field property, that's why even though it is set to six it will let you enter more characters.

tarbat

  • ShipTrax Beta Testers
  • Hero Member
  • *
  • Posts: 4219
    • Radarbox at Easter Ross
Re: A380 Database Info
« Reply #16 on: March 19, 2008, 06:24:25 PM »
SQLite does not support the VARCHAR field property, that's why even though it is set to six it will let you enter more characters.

SQLite does support the VARCHAR type, it just doesn't enforce the length :(  I stand corrected.  It's up to the programme to validate field length.