The hoster panel shows that they are connected, and phpMyAdmin indicates that the database user has no data, and I can't create another user because it's not a tariff.

I don't believe you're doing that chat right now. The server has a database with registered users. And for messages, another database. Each chat matches the table. In each table, messages. At the beginning, the application sends a request to the server and comes to me. JSON rooms. In the case of a room, the last 30 messages are requested. The auto-loading of the messages takes place upstream. Your idea is ideal. Imho, that would be what any developer would have done.

It depends on the task you have. I suspect that the format of the date does not change by accident for the same field. A suitable format should therefore be used for each of them. For the date(full or not) to use timestamp, I would have chosen for time. integer=hours*60*60+minutes*60+secondsbut the incomplete date will remain as yyyy-mm-dd 00:00

I just needed to change the BD version by 3 Why not?

When you see a strange mistake in the logs, you need to:Copy that part where there are no specific words. open failed: EACCES (Permission denied)Smash her in the google and cross her first. https://stackoverflow.com/a/9907574/3212712 There's an answer, you don't have permission to read the files from the device. I mean, you should add to the manifest:<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" /> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /> On the same reference, there is also a mention that some authorizations from API constituent=23 (Android 6+) should be requested in the ranks. The code is how to do it, too.

On reading from the fragment, according to your code, you must address your local base. The version of the OBD in this case is determined by you. So it has nothing to do with the OBD version. So, when your local BDE is opened, use the designer:mDatabaseHelper = new DatabaseHelper(this); If the data change to the OBD, the version should not change. The version of the OBD should be changed when its structure is changed, and since your OBD depends on cloud-based OBD, you will change your OBD when the OBD changes in the cloud. At the same time, you'll have to redesign the Upgrade method to your class.

Everyone is so confused as to how the information is identical, but for example, it is possible to: //добавление новой новости public void addNews(String addNewNews) { //проверка наличия новости в БД // вытягиваем курсосром новости из БД cursor = db.query("news", new String[] {"news"},null, null, null, null, "news ASC"); //пробегаем по курсору и ищем идентичную новость if (cursor!=null){ cursor.moveToFirst(); while (!cursor.isAfterLast()){ availableNews = cursor.getString(0); if (availableNews.equalsIgnoreCase(addNewNews)){ Toast.makeText(getApplication(),"Новость существует", Toast.LENGTH_SHORT).show(); cursor.close(); return; } else cursor.moveToNext(); } insertNews(addNewNews); } }

If read carefully https://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html#delete(java.lang.String,%20java.lang.String,%20java.lang.String[]) To the methods, it may be noted that the condition for disposal will be transferred as a second parameter. That is, the method must be given:db.delete("news","_id=" + id , null); or so:String[] whereArgs = new String[]{String.valueOf(id)}; db.delete("news","_id=?" , whereArgs); The second option would be preferable to exclude the use of sql injections.

if (cursor.moveToFirst()) { ArrayList<String> values = new ArrayList<>(); for (String columnName : cursor.getColumnNames()) { values.add(cursor.getString(cursor.getColumnIndex(columnName))); } for (String value : values) { Log.d("TAG", value); } }

You can put the finished OBD in APK. It's preferable because it's easier on the computer to prepare the OBD system and it's possible to properly test requests before using the cadet sample.I used to fill and test the OBD. http://www.sqliteexpert.com/ - free and quite powerful SQLite base manager, who performs almost all the functions that are in the payroll. You can also test the queries when you get a visual, not a cadet you can't look at. The database is in the catalogue. /assets The application is a simple copy of the file in this project folder, but it can't work from there because it's a folder for static (unchangeable) resources and should be codified in the section on the device assigned to your application (usually, it's not a folder for static (unchangeable) resources. /data//data/<package_name>/databases/where your annex is authorized to record and other files.This can be done by using your own code. https://ru.stackoverflow.com/questions/488797/%d0%9a%d0%b0%d0%ba-%d0%bf%d0%be%d0%b4%d0%ba%d0%bb%d1%8e%d1%87%d0%b8%d1%82%d1%8c-%d0%b2%d0%bd%d0%b5%d1%88%d0%bd%d1%8e%d1%8e-%d0%b1%d0%b0%d0%b7%d1%83-%d0%b4%d0%b0%d0%bd%d0%bd%d1%8b%d1%85-sqlite-%d0%b2-android/488845#488845 or a ready library https://github.com/jgilfelt/android-sqlite-asset-helper which is preferable (then the base falls into the catalogue assets/database/ Annex)After copying, this OBD needs to be used exactly as if it was set up on the device. The actual difference is only that in the first case the OBD is copied, the second is initially created there.PS: If the size of the initial OBD (what you put in the catalogue) assets/() More than one megabyte, the extension for OBD should be specified as for the non-compressed type of data (*.png, *.mp3), not *.bd or there *.sqlite, because the catalogue assets/ is subject to compression and there is a limitation on the size of the files for this operation at 1 Mb.You can also fill the OBD right on the device. To that end, we're gonna have to set up some sort of structure with data like XML or JSON file, disassociating that you're gonna fill up your OBD record for the record. This is longer on the first start of the application than copying the finished OBD and is not so easy to test, but slightly less on the final APK size and has no restriction on the initial OBD dimension.

Better use Oracle Database XE. It's less fun, it's easier to remove, operational memory uses 1 b, a processor, free, and there's a graphic interface like PMA. Besides, she's not old at all. The last version is as much as 11.2.

It's a general algorithm of action in coping with data on the auto-increment field. How do you do that with the Android? If there are no other tables with the floors referring to this auto-increment field (or other fields in this table referring to it), then simply copy: Instruction insert database.schema.table (fieds) select from ... and on the list of the fields of the target table, and on the seclet, you don't mention this auto-increment field. That's it. Only if... If there are tables with the floors invoking this field, it will first be necessary to establish a time table with two layers, old and new ID. Fill it (as long as the field is 'old ID') all the lines to be moved (this is 1 request insert-select) further to the main copying of the cadet, fast + receipt of the new ID and maintenance of its interim table (the last ID - variable @@identity to be read immediately after each induction operation, e.g. select @newid = @@@@@identity )Once the core table has been moved, we copy the references to it (one request), and the field value is changed from the old to the new (instruction insert-select and in the grid adding to the time table with the connection - field reference = 'old id')If there is a field in the main portable table referring to the ID auto-incremental, then another field is needed in the time table - 'old reference to ID' (also provisionally retained, in the same request as 'old ID'). With the main copying, the target table replaces any existing ID values in the new table. After major copying by one request (with joining the time table, replace the meaning of this reference to the current new table)If ID conflicts are not foreseen (e.g. target table - empty) and associated tables should also be copied, the keys could be copied without recosting. Just temporarily disconnect the auto increment rule, copy as it is, with all fields. Then insert this rule back:SET IDENTITY_INSERT [ database_name . [ schema_name ] table OFFSET IDENTITY_INSERT [ database_name . [ schema_name ] table ON

No, it's impossible to limit the number of records, but there's one trick that can help:Setting up the tableFill it with hundreds of records, each one millisecond above the previous one.In lieu of a requisitioning operation for the oldest record

SQLite is a language of request, it would be unnecessary to give it anything other than generating requests and a sample of OBD. And don't forget that he's still LITE, that is, many of his possibilities are limited to the need.

The question was very simple. It's just that all components related to the Dana database are on the same form as the table on buttons and the treatment code for what is related to the OBD. In short, if TIBDataBase is in a different form, nothing good will happen.

DB access under Android will not work. So if you want to deliver the OBD together with the Android program, use the SQLite in connection with FireDAC. How to do this on the steps described http://docwiki.embarcadero.com/RADStudio/XE7/en/Mobile_Tutorial:_Using_FireDAC_in_Mobile_Applications_%28iOS_and_Android%29 ♪

http://doc-prg.narod.ru/index_1cv8.htm Work has been reviewed with 8 of Delphi in all details.

That's why you need to create a record of interaction with the server.Create a violin (API) on the server working with the OBD postgresCreate a module on Android that goes to APIEstablish a base synchronization module that works with API and OBD SQliteit is not recommended to operate directly with the base on the server. Better use this method.

Well, if you follow the structure I have proposed, it looks like: Id Parent_id Name 1 0 Обувь 2 1 Мужская 3 1 Женская 4 1 Детская 5 4 Летняя/Зимняя 6 5 Кожаная/не кожаная/совсем не кожаная 7 6 Китайская/не китайская/японская

Use it. UPDATE:UPDATE GradeTable SET StudentID = :param1, StudentName = :param2 WHERE TeacherID = :param3;