Good morning,
I'm developing a cms.
Before I was working with Access but I was limited so now I'm changing to MySql and I have some problems about the creation at run time of the db.
When I was using Access I connected with OLEDB and I used the object Adox to develop on the fly databases.
Now I don't know how to do, I found a lot of articles for Sql Server but nothing interesting for MySql.
Is it possbile to do it?
When I connect I must to put the name of db but I dont have yet.. so..
Anyone has already developed something similar?
Thank you
Related
I'm creating a mobile app for an existing website and trying to connect to a local instance I have running on a MySQL workbench. I've seen others recommend against the use of MySQL but I'm stuck with it, since that's the current database. I'm using expo to run my React Native code. Do I need to use a server, like "MAMP?"
Let me know if there is any more info that is needed.
You cannot connect your app directly to your database.
You will need a server/API that acts as an intermediate between the app and the DB. You can code it in most programming languages and if you know PHP, having MAMP on your system will allow you to build your API with PHP.
I've seen others recommend against the use of mySQL
You should definitely question their reasoning. I've been using MySQL for many years now in small and big projects and it has never been an issue. If they're comparing it to non-relational DBs like Mongo, I can understand, it's easier to setup and maintain a NoSQL database than a relational one.
I assume you're not that experienced but I still purposefully used some terms that may be new to a beginner. Since I don't know your skills, I will refrain from pointing you to specific tutorials/articles.
I recommend you to Google anything you don't understand from this answer.
Forgive me if this is a silly question, just been scratching my head for hours on this and cannot find a decent answer!
I'm writing a script to install a Laravel CMS to a database and would like to have it create the database from the given name if it does not exist.
I am at the stage where the system understands that the database does not exist and so needs to create it, But every time I run my code I get the exception:
SQLSTATE[HY000] [1049] Unknown database 'mytesting' (SQL: CREATE DATABASE mytesting)
I'm running the code as follows to initiate the database creation:
DB::statement(DB::raw('CREATE DATABASE '.$_POST['DbDatabase']));
Now, I can understand that this may be crashing because the database name set in the .env is that of a database that is yet to exist, but I am wondering if there is a way to have the system simply auth to MySQL via login (No db name specified) and then create the table?
I've run the provided sql inside Sequel pro and it works there so I know it's valid, But am confused all the same!
If any yall could shine some light on this I'd be eternally grateful!
Thanks guys <3
I finally managed to figure out a way around this!
So instead of using Laravel's DB manager I ended up using a PDO instance instead as I could control what it did at a much more granular level. I specified the connection details out of the env file.
Thanks so much for your help guys <3
I am using MySQL DB for my android application. I have installed phpmyadmin on my Ubuntu LAMP server and using it to access my DB. Is there any possibilities to access the DB using MS access 2010, as I need to do perform modifications on a regular basis to my DB
If the aim is to change the data and not the structure, using MS access is a good solution, as you can edit anything in linked tables very efficiently with litlle setup efforts.
To achieve this, first you need to download and install the MySQL ODBC driver.
In order to avoid issues, I advise you to install the 32 bit driver, even if you're on a 64 bit system. The 32bit will work flawesly, which is not always the case of the 64 bit.
Once installed, open the ODBC control panel and add an entry pointing to your MySQL database
Then in Access you can add linked tables using this ODBC entry
Once the table are linked, they will behave as if they are MS access tables and you can open them and edit data, and much more.
You can use Microsoft Access as a front-end to your MySQL database.
Refer: MySQL Documentation
But for your case, directly accessing database is wrong. I suggest better you have a view page with php to update DB with proper required validations.
The answer by Thomas G does an excellent job of describing WHAT we need to do, and even provides some good links.
What we need now is a good, step-by-step description of HOW to accomplish all the steps Thomas G describes.
I've been looking for this for a long time, and still no luck. However, I'm possibly on the track of getting that answer, and if I find it, I'll come back here and post it.
I have an ACCESS database(.accdb) with tables, forms, queries, reports , modules and microsoft access class objects(VBA code). Now the requirement is to shift from access to optional database. The options that I could find by browsing are using either MySQL or SQL Server. As of now, I would like to use Access as front end to any back end database. I would like to know more detailed information regarding migration from Access to optional database. Can anyone please help me or point me to good resources.
I've used SQL Server as a backend for an Access front-end app in the past with pretty decent success. You can use the SQL Server Migration Assistant wizard to migrate the data from an Access Database to a SQL Server database.
Performing a quick search for "using SQL Server database as back-end for MS Access" will yield a number of resources on things to consider and do. You can also refer to this SO Question Can a Microsoft Access Forms application be switched to work with a SQL back end? for additional insight.
My experience has been pretty positive with this sort of migration, but it really depends upon how you've designed and constructed the application. It could be a very simple migration (a few hours to tweak and test things) to a much larger effort on your part to make sure everything works as expected.
You can use SQL Server (Express) as backend using export data from Access Menu. If you will use MySQL some features like auto_increment fields don't work fine and it will need to write VBA code to work as expected.
We have ROR site with a MySQL database. There are many tables which we would like read/write access to, but we have not written this function within our current admin panel. I was curious the drawbacks of using an ODBC tool to perform all reading/writing of values to the database from the admin panel. Also, does anyone have any suggestions for ODBC tools that we should look into for an easy to use software.
I think that you haven't actually started using Rails, else you wouldn't ask this question. Go spend some time reading the documentation and a few getting started tutorials.
http://guides.rubyonrails.org/
Rails comes out of the box with ActiveRecord, an ORM layer. Once you get familiar with it, reading/writing to the database will be a breeze, independent of what database you are using.