I have created an Access DB with a nice front-end, however the db is not split.
The DB is in a network location and it is shared between 5-8 users. Data loss occurs from time to time: some stored queries just disappear when sending their output via e-mail through a macro, for example.
I have read on several sites that to prevent this, I should split the db and make each user work on his/her frontend.
However, in the context I am it would be much better to have the users working on a single shared file.
The question is: If I split the database and make the users share the front-end file, would I be preventing data loss/corruption?
Related
I have a question about web3js.
If my site will load data directly from blockchain (MetaMask) without loading them into the database, and immediately through js bring them to the site then:
1. If a large number of events (1-10 kk) then analyze them on the side of the browser is a bad idea? Need to record everything in the database and the user to publish the analyzed information from the database?
2. When a user enters the site, then in fact his browser parses the information out of the blockchain (if using MetaMask)? Not my server. And I do not care how many connections go through web3js at the same time
What the best?
1. Get all data with web3js and show them on site.
2. Or get all data and writing to database, then use ajax for dinamic show data?
I'm new here. I am currently enrolled in a Data Analytics degree program. I looked through the past questions but I could not find an answer to my question.
Here is my question. Let's say you have a plain and simple HTML form on a webpage. Each field is connected to a certain column on the database, correct? Like your first name and last name.
What if someone wanted to store the username and password on it's own separate database on a completely different server. How does the software know to send those form fields to a completely different database? Does it work off of IP? I'm really confused as to how this is accomplished.
This is a very high-level summary of what happens but hopefully it makes sense.
When the user submits the form, the form data on the HTML page is sent to the web server through an HTTP request. The web application then processes this request and typically uses a connection string (which includes information about the database) to connect to the database and update the database appropriately. Each field in the form does not have to be directly associated with a field in the database. For example, the application may be coded so that multiple fields are concatenated into one database column. The connection string can use either hostname or IP address, but hostname is typically used as it is more human readable.
When one wants the application to send data to a different database, they can just modify the connection string. This is typically done during web app development when switching environments. For example, in the attached diagram, if I wanted to use the production database instead of the test database I could modify the connection string within the web application so that it is pointed to the production database by simply changing the hostname in the connection string.
I wanted to save all my data from firebase database into a local database in (JSON format only) for my application to access it when not connected to internet. It consists even images in it along with string form of data.
Firebase allots very less space for offline mode saving data into the application hence can't use it.
I want data to be first saved in my local database and then to be retrieved into the recyclerView of my application.
Moreover I want to save login details as well as other user specific details required to keep the application function without internet into particular user's login.
Searched for answers but no reliable or step by step guide I encountered.
Are these things possible? What should I do ? Please guide.
We're using Cloudant as the remote database for our app. The database contains documents for each user of the app. When the app launches, we need to query the database for all the documents belonging to a user. What we found is the CDTDatastore API only allows pulling the entire database and storing it inside the app then performing the query in the local copy. The initial pulling to the local datastore takes about 10 seconds and I imagine will take longer when adding more users.
Is there a way I can save only part of the remote database to the local datastore? Or, are we using the wrong service for our app?
You can use a server side replication filter function; you'll need to add information about your filter to the pull replicator. However replication will have a performance hit when using the function.
That being said a common pattern is to use one database per user, however this has other trade offs and it is something you should read up on. There is some information on the one database per user pattern here.
I've been trying to implement authentication and session management in a node.js application using socket.io.
And from almost all the resources I found, I came across the term "session store".
There are open source tools that handles sessions for us, but we have to provide them with a session store.
Some tools has built in storage for sessions in memory, for example the module express-session comes with a default in memory session store, but also this warning:
Warning The default server-side session storage, MemoryStore, is purposely not designed for a production environment. It will leak memory under most conditions, does not scale past a single process, and is meant for debugging and developing.
So I searched for the available stable session stores and it turns out that most of the names are databases that I've heard of.
For example, here's a list of session stores and another one at GitHub that I've came across.
The names include MongoDB, MySQL, SQLite, cassandra, firebase etc, hence the confusion.
So the question is, are session stores and database the same..? (I can think of it like - when we're using the database for storing session details we call it session store but it's in fact a database)
If not, how do they differ..?
Session store is a place where session data is being stored on server.
On web its usually being identified by a cookie stored in clients browser.
So it allows your app to identify user and keep him logged in for example.
Session can either be memory, some database, simple files, or any other place you can come up with to store session data.
If you project uses some database, you can configure your session store to use the same database, to avoid having another database on server just for the purpose of session store.
Differences between different session stores:
Memory session store is going to be reset on every app re-lauch. Also its fastest.
Database session store, is going to be safe with app
re-lauch. And at some point you will have alot of session objects
which you might want to clean up. And same session stored in database can be even accessed from different apps.
Session store is a method of storing information about user as a session with unique identifier. It could be stored in memory or in database. Socket.io can utilize the same session (id) being used in express app by socket-express-session package, if I am not mistaken.
You can then use session information to grant/restrict access, for example.