Hi there,
I'm running into a slight design issue with URLyBird 1.2.2, or at least I feel I'm having to go with a sub optimal approach :
The DBAccess interface, and thus the Data class the instructions tell you to implement use
string arrays for record data. My planned design was as follows :
FileDatabase -> Data (DBAccess) -> some room management facade class
Apart from the file database class Data would also have a seperate lock manager to implement the required locking mechanism.
Now, the issue is that initially i made a Room "entity" class to represent a single record to be used throughout the application. But because the DBAccess interface forces string arrays as records it'd be odd to have the FileDatabase class work with Room objects, then convert them to string arrays for the Data end of things, and then right back to Room objects for the facade.
Basically it seems as if the instructions are intended to make you deal with String arrays as the representation for record data throughout the application.
Is this intended you think? And if not how did other people solve this design issue?
Any thoughts or input would be much appreciated, and my apologies for the lengthy and perhaps slightly incoherent post