Can I Use Different Price For Google Product Schema in Magento 2.3?

I have an attribute called google_price. Can this be used in the product schema for Google instead of the price listed in Magento?

I’m looking at my final_price.phtml file and it only uses the "final_price" ID.

Data model and database schema

I need to test my understanding of the difference between the data model and database schema. According to my understanding, the data model is a description of how the data will be stored and the relationships between the data. While the schema is very similar to a database model and according to the book “Database Management systems ” by Raghu and Johannes ” A description of data in terms of a data model is called schema” and it’s a template of how the data will be stored. Is that right?

Postgresql identify column name information from table schema

I have multiple tables with with varying names for the same piece of data. For example, day vs business_day. I’d like to identify what column names exist for which table. I think this can be done using schema information, but I’m not familiar with it.

For simplicity, the tables below are 3 separate tables with these column names.


day    city  weather


business_day location  status


day   city  rain

Where day and business_day and city and location are the same piece of information, but unfortunately different naming conventions so I wouldn’t be able to use the same selection criteria in a WHERE clause. I’d like to search the table information to see which tables have day or business_day and city or location. The other columns are not important to me in this example. How can I identify table information in this way?

mongoose – Referencing the photoCode schema inside the model schema

Hi there I would like to know if there’s a better way of specifying an array of objects on a mongoose schema.

This is what I have at the moment:

const mongoose = require('mongoose')

const photoCode = mongoose.Schema(
    value: { type: String, trim: true, unique: true },
    status: {
      type: String,
      enum: ('valid', 'expired', 'attributed'),
      default: 'valid',
  { strict: true, timestamps: true },

const photoCodeSchema = new mongoose.Schema({
  code: (photoCode),

module.exports = mongoose.model('PhotoCode', photoCodeSchema)

sharepoint online – How to add default folder in document library Json Schema – Team site

I would like to add functionality to my script to add a default “Archive” folder to Document library. It would be good to add in the upper part of the screen an explanation what files should be there.

Currently the structure looks like this:

General files (Document library)
in the middle the folder “Archive”.

Here my script, which creates document library:

        "verb": "createSPList",
        "listName": "General files",
        "templateType": 101
        "verb": "addNavLink",
        "url": "/General%20files/Forms/AllItems.aspx",
        "displayName": "Client documents",
        "isWebRelative": true

I don’t see any parameter here that specifies creating an empty folder in document library.

Create a new SharePoint list

ER Schema – bank system

Hello i’m trying to model a simple banking scheme
where I have 3 transactions: withdraw, transfer, deposit.
of these 3 operations, the transfer is the only one that needs more attributes, I need to know the accounts participating in the transfer, and who received and who sent it.

At first I thought of something simple like that, but it seems very strange:

enter image description here

but this seems very vague to me, and when do I need the statement from the two accounts participating in the transfer?

could someone help me with this?

database design – The most generic e-shop DB schema

Let’s say I create a schema for an e-shop what potentially sells everything: laptops, phones, tires, snacks etc.
Considering this, I cannot create a new table/entity for each good category the shop sells and describe the good’s properties by new attributes.

So, I went to more generic model to describe each product

To me, it seems fine but as soon as I’ve tried to implement this solution, it’s appeared to impossible to execute any query like

select names and prices of all laptops where ssd capacity >= 512 and weight < 2kg and price <= 2000 money

How is possible to change this schema and keep the ability to store information about any product?

Postgres: Efficient schema for querying with one exact string match and two range matches

The table I need to query:

CREATE TABLE regions (
    state text NOT NULL,
    zip_begin text NOT NULL,  -- 9-digit zip code
    zip_end text NOT NULL,
    date_begin date NOT NULL,
    date_end date,

    data ...,

There are ~50 states and between 0-5M rows per state. The zip and date ranges might overlap.

The following will be one of the most common queries in my OLTP application:

FROM regions
WHERE state = {state}
  AND {date} BETWEEN date_begin AND date_end
  AND {zip} BETWEEN zip_begin AND zip_end

This query usually yields one row, but may sometimes yield more.

From the Postgres docs, it sounds like a GiST index might do what I need, but I don’t really understand how those work.

schema – How to represent Hierarchical data in Redshift when using OBT denormalised table design

We are loading a fairly simple dataset with 50-60 columns into Redshift in a flat One Big Table denormalised design (with just time dimension and one other split away). It will represent an immutable store of business events, so works well with the Redshift style of MPP and this approach reduces the complexity of managing the surrogate keys, SCDs and joins which slow Redshift down.

There are a number of hierarchies in the data.. not a huge distinct number of values and no branch should ever go beyond 4 levels and the data is largely very static.

With limited datatypes designed for this compared to other RDBMS and no recursive datatypes, what is the best way to store the hierarchical data in Redshift ?

Early thoughts – Have each reference value have 2 extra columns for parentId and hierarchy level ?
configure in views or push downstream to the BI tools to configure the hierarchies? (RStudio, PowerBI)

information schema – How to use a query to get the definition of MySQL database objects (specifically the variables they use)

I have written a query to get most of the useful information about the routines in a MySQL database for a database documenter that I am developing.

The code below will return routine name, routine type, routine param list, routine return value (if any), routine definition and routine comment (if any).

However I can’t seem to work out how to return any variables that are used by each routine (either local or session)

Can anyone help me out with the code to get that extra column displayed in my query with the variable names in it?
(Be good if they were concatenated as I have done with the parameters but that’s not too important.)

I would stress that the databases are held on a remote shared server so I cannot log in as root, nor can I access it as local host. ie for example, access to tables like ‘proc’ and ‘users’ and others that would be available to an admin user are denied

The code I have so far that returns most of the information (also included in case it’s useful to anyone else)

SELECT routine_name, routine_type, routine_param_list,routine_returns,routine_body, routine_comment FROM (

    `information_schema`.`events`.`EVENT_NAME` AS `routine_name`,
    'EVENT' AS `routine_type`,
    '' AS `routine_param_list`,
    '' AS `routine_returns`,
    `information_schema`.`events`.`EVENT_DEFINITION` AS `routine_body`,
    `information_schema`.`events`.`EVENT_COMMENT` AS `routine_comment`

    `information_schema`.`routines`.`ROUTINE_NAME` AS `routine_name`,
    `information_schema`.`routines`.`ROUTINE_TYPE` AS `routine_type`,
          ' ',
          ' ',
        ) SEPARATOR '; '
    WHERE `information_schema`.`parameters`.`SPECIFIC_NAME` = `information_schema`.`routines`.`ROUTINE_NAME`
    GROUP BY `information_schema`.`parameters`.`SPECIFIC_NAME`) AS `routine_param_list`,
    `information_schema`.`routines`.`DTD_IDENTIFIER` AS `routine_returns`,
    `information_schema`.`routines`.`ROUTINE_DEFINITION` AS `routine_body`,
    `information_schema`.`routines`.`ROUTINE_COMMENT` AS `routine_comment`


      `information_schema`.`tables`.`TABLE_NAME` AS `routine_name`,
      `information_schema`.`tables`.`TABLE_TYPE` AS `routine_type`,
       NULL AS `routine_param_list`,
      '' AS `routine_returns`,
        'Algorithm: ',
      ) AS `routine_body`,
      '' AS `routine_comment`

          ON (
            `information_schema`.`VIEWS`.`TABLE_NAME` = `information_schema`.`tables`.`TABLE_NAME`
    WHERE `information_schema`.`tables`.`TABLE_TYPE` = 'VIEW'
    ) AS T
--   where routine_name = 'MyRoutine'
--    and routine_type = 'MyRouitineType'