First I would like to explain why I want to use alternate Blackberry Persistance options rather than a Blackberry database itself, say SQLite. The reason is that the application i'm designing, I want it to be used in all the previous versions of Blackberry rather than just the ones having OS 5.0 or greater.
Now, coming back to the actual question, I have got a database that I want to replicate to be used in the Blackberry application. The database has 8 tables and each table has approximately 12 different columns. One of the table has 1000 rows. Now if I was to implement this DB for a Blackberry application , keeping in mind that it will work on all the versions of Blackberry, what would be the best way to implement it?
Take a look at this post for some DB alternatives that would work pre-5.0, such as SQL Anywhere for BlackBerry
Related
This question already has an answer here:
How to make offline database for my app?
(1 answer)
Closed 6 years ago.
I'm currently working on an application in Xcode 8/Swift 3 which runs through APIs. Essentially, I'm parsing information using SwiftyJSON from my MySQL database which keeps the content current and easily updated.
To keep it so the content is also available offline, I'd like to introduce a facility where the data is downloaded and stored on the phone so it is available in "offline mode".
I know it's a completely open question but can anyone point me in the correct direction of how I could make this JSON information available offline? I've tried searching the net with no success.
I know it's not Swift, but the absolute master of this has recently open sauced his master piece: Dash for iOS.
Reviewing what he's done to get rapid scrolling and searches might give some deep insight into how to best do this as done by someone with (arguably) more experience in this area than anyone other than Apple:
https://github.com/Kapeli/Dash-iOS
I will prefer here 2 option either I will go with 1.SQLite DB or 2. NSURLCache
For SQLite DB you can use FMDB wrapper-https://github.com/ccgus/fmdb
For NSURLCache check this link Best way to Cache JSON from API in SWIFT?
If you just want to save json then go with NSURLCache for offline mode.
Achieving offline for iOS is having two best paths they are CoreData and SQLITE. As per the definition of CoreData suggests it is a Model layer of the project. It comes with less efforts on developer side. Bit contrast SQLITE having the same way but little efforts on it.
In my project we are using the CoreData for offline maintenance. Really we have few concerns on the Relational data fetching, Although there is a Predicates representing CoreData for the same still it is limited to some part. These type of situations SQLITE is really a life saver. We can easily fetch the records with simple JOIN commands.
Conclusion:
If you have more complex data relations it's really better to go with the SQLITE, Apart from CoreData is best choice.
My iOS app is a mobile version of a management program I had developed for a company as a desktop application. So its main tasks are saving data in a database and retrieve them when needed with the option to edit them. So I guess that the GUI is mainly composed by forms to fill in and tables to show data. So I am asking you if you could link me some tutorials or give me some tips on how to realize them in a nice way but not too complex. I'd rather avoid simply creating a blank view controller and inserting labels and text fields without a minimum of criterion. I am very new to iOS and XCode and, as I have not too much time, I am asking directly your opinion instead of spending hours in looking for tutorials.
UPDATE!
I mean that I would like to get something similar, for a mobile iOS device, to the following screenshots (from the desktop application I mentioned above)
Seems that you need a grid control to do it.
You can develop your own, or use existing library.
I have very good work experience with Infragistic http://www.infragistics.com/products/ios/grids/grid-view-layouts, but maybe DataForm from Telerik will be better in your case http://www.telerik.com/ios-ui/dataform
I'm looking for a design guideline for large data entry in iPad application.
My application consist of more than 30 text field in one page that users have to input data in every each of them. My plan is to find the best way to have a user friendly app and easy to do the process as far as having a good design in the application.
Any suggestion?
Not sure how kosher this is to pimp my own stuff here (not like I make any $$ from it) but I've developed an open-source iOS project that handles quite nicely and easily just what you're looking for - user-friendly form/data entry.
https://github.com/mamaral/MAFormViewController
I'm planing to create an app for iOS which will be kind of informative application for public transport in my city. People will enter street name from where they want to get public transport and will get list of buses and minivans, which are traveling by that street.
My problem is that I'm just started developing for iOS and want to find easy method to create a database/table with simple information as streets name and bus numbers that will connected with those streets.
So basically I need to create database/table and an search-box which will be connected to that database.
From where I need to start? Thanks.
p.s. - sorry for my bad english ;)
SQLite is quite popular and supplied by Apple. This lets you manage your table, and allows most standard SQL queries. You can also link to Core Data if you want to treat your data as objects.
See the Apple overview
There are many tutorials to build a simple app with a table view using SQLite, e.g. here or here
I found the Stanford University videos a good way to learn this stuff, e.g. here on YouTube or there are later versions available in iTunes U.
Yep, for an on-phone database SQLite is the way to go for a full-featured database, or Core Data if you want some "hand holding". And, of course, if you don't need persistence you can make a pretty good database simply using NSMutableDictionary and maybe a few custom classes.
Learn to use CoreData. Its not there to "hand hold" you, its there to provide a complex and optimized ORM interface for the underlying SQLite database-- there are a number of optimizations implemented to improve efficiency. You could pick it up in a night following tutorials and online instructions.
I am looking for a how to create a mysql database with the photos which are uploaded by my iOS app.
I have already programming the picker and the upload part, but I have no idea how to create this database considering that will have 3 different voices "localization , type , date ".
Do you mean a database on the iPhone? If on your iPhone, the typical solution is sqlite. I personally use an Objective C wrapper, FMDB for that, that gets you out of the weeds of sqlite programming. Or check out Core Data if you want to be a little more Cocoa about it.
If, as I suspect, you're talking about your server database, then this is probably not the right forum for that question about how to create a server database. You need to be more specific, and include code samples of what you've tried.