I have a Lightspeed POS 3.x Backup file. I would like to abstract the database out of it. Is this at all possible? The file extension of the backup file is .lightspeedBackup.
I believe you should be able to just rename it as a .zip and extract it. Once you do you should have several directories and files with all your data in it.
Not sure why they try to hide that or are using their own extension.
Related
I am trying to figure out how to include a pre-annotated model in Watson Knowledge Studio. I have followed the information found here but it doesn't seem to generalize. As a start I have tried exporting an annotated set from Knowledge Studio to re-upload (using the "Import corpus documents and include ground truth" option). If I re-upload the exported zip as-is this works but if I unzip the folder and then recompress it I get the following error:
A file could not be imported: The imported ZIP file is not in the expected format. Check whether the file was exported from another project. The type system from the same project must be imported first. (You selected 'Import corpus documents and include ground truth').
I have tried using the zip command in Linux (both with and without the -k flag which tries to force to MS-DOS style naming) and also used the compress utility in Windows but I get the same error each time. This is without making any changes to the contents of the folder.
Any help would be greatly appreciated!
Would you please check internal structure of your created ZIP with comparing the original ZIP ? Sometime I got the similar trouble report and found that their created ZIP contains root folder in ZIP structure. WKS expects the same folder structure in the ZIP file.
I am working on drupal 7 which has content type that has a filed "file" and the file is uploaded to mysql database.
I would like to find the table where the file is stored as binary BLOB type.
Know the node ID.
Unless you have something special installed that I'm not familiar with, the files themselves aren't stored as binaries/serialized/etc in the DB. The file table (or is it the filr_managed table? I apologize, I'm on my phone and will try to answer more fully when I sit down at a computer) just stores things like the file id (fid) and the path to the file.
As I understand it, storing the files themselves, fully in the DB would lead to some pretty heavy/intense DB call times.
I'm not sure if this is a reason why you expect it to be in the DB, but if you are looking for the files to be accessible following their nodes access, you'll want to look into setting up private file storage outside of the Drupal root directory.
If you have a default configuration, you will find your files in the filesystem, in the following subdirectory of your Drupal installation :
drupal/sites/default/files
If you want to store all the file in the DB, tou can by using a hook on saving file, but it is not recommended for performance reason. Better to acces a file by URL than download it from database.
I don't have access the original executable files but only the runtime versions of the Access files. I need to change a key core function of a database and I cannot access the core functionality. Do I need the original files or can I work with what I have?
The .accdr file extension does not tell you whether the database is actually ACCDB or ACCDE format. If it's ACCDE, source code was removed and you can not use it for further development.
Find out which you have:
Make of copy of the .accdr and rename that copy with an .accdb file extension.
Open the .accdb in Access.
Attempt to open any module and view its source code.
If step #3 is successful, your database is an ACCDB and you can make design changes to it.
If step #3 fails, the database is probably an ACCDE. You will need to find the original ACCDB to use for your design changes.
In Gradle, I would like to:
1. Specify a database file (e.g. .mdf file) as a dependency.
2. Attach that file to database instance.
I know how to do #2, using file path.
I don't know how to get file path of a downloaded dependency.
Please have a look at this question - it's quite self explanatory. However I suppose that better idea might be keeping the mdf file under src/main/resources. Why don't You put it there?
Hey. I need to upload some files (images/pdf/pp) to my SQLS Database and thereafter, download it again. I'm not sure what is the best solution - store it as bytes, or store it as file (not sure if possible). I need later to databind multiple domain classes together with that file upload.
Any help would be very much apreciated,
JM
saving files in the file system or in the DB is a general question which is asked here several times.
check this: Store images(jpg,gif,png) in filesystem or DB?
I recommend to save the files in the file system and just save the path in the DB.
(if you want to work with google app-engine though you have to save the file as byte array in the DB as saving files in the file system is not possible with google app-engine)
To upload file with grails check this: http://www.grails.org/Controllers+-+File+Uploads