pic field in dbpro
Quote from s7shanbe on January 16, 2020, 7:55 pmhello everyone
in neobook dbpro can be saved any file type in picture field?
If this is possible please help.
hello everyone
in neobook dbpro can be saved any file type in picture field?
If this is possible please help.
Quote from farhad2008 on January 17, 2020, 7:50 amhi,
Use the blob typeregards
hi,
Use the blob type
regards
Quote from PaulJonestindall on January 17, 2020, 5:27 pmIt depends on what type of DB file you're using. For example, I use Access MDB files to store tiny JPG files (1K) but when looking at the raw table data in Access, it shows as binary data. Presumably you can store whatever file type you'd like. In my case, 1K JPGs are not much of a consideration, however dealing with a multitude of PDFs, I use a string field containing a link to the file.
It depends on what type of DB file you're using. For example, I use Access MDB files to store tiny JPG files (1K) but when looking at the raw table data in Access, it shows as binary data. Presumably you can store whatever file type you'd like. In my case, 1K JPGs are not much of a consideration, however dealing with a multitude of PDFs, I use a string field containing a link to the file.
Quote from mazzu001 on January 18, 2020, 5:51 amYes it can. In some cases you may have to change "picture" to "image" (depending on what database you are using) but in either case its binary data (blob) field. The file size itself can be quite large. But there can be problems with loading a table if you have a large table. I have a table in a database with over 3000 sound files stored in "image" field type. Loading the table using VisualNeo Wins "dbploadtable" command takes a very very long time. In this case I just use "dbpSqlCommand" and use search queries like "SELECT * FROM sometable WHERE something = 'somedata';"
A BLOB can be 65535 bytes (64 KB) maximum. If you need more consider using: a MEDIUMBLOB for 16777215 bytes (16 MB) a LONGBLOB for 4294967295 bytes (4 GB)
Yes it can. In some cases you may have to change "picture" to "image" (depending on what database you are using) but in either case its binary data (blob) field. The file size itself can be quite large. But there can be problems with loading a table if you have a large table. I have a table in a database with over 3000 sound files stored in "image" field type. Loading the table using VisualNeo Wins "dbploadtable" command takes a very very long time. In this case I just use "dbpSqlCommand" and use search queries like "SELECT * FROM sometable WHERE something = 'somedata';"
A BLOB can be 65535 bytes (64 KB) maximum. If you need more consider using: a MEDIUMBLOB for 16777215 bytes (16 MB) a LONGBLOB for 4294967295 bytes (4 GB)