linux – LibreOffice Calc Copy / Paste in Google Spreadsheets skips blank lines

The problem is that copying the selection area from LibreOffice Calc to Google Spreadsheet copies the result with missing blank lines. In the row of the selection all cells must be empty so that they can be skipped.

This behavior caused me some problems because the inserted data was shifted up by the skipped number lines. My eye did not notice the fact and I have some problems at work.

I have LibreOffice version 6. The source file is in Microsoft XLSX Format.

Could someone show me how to turn this feature off? Maybe it's a google thing? Every advice is appreciated.

Thank you very much

python – Panda does not create any new spreadsheet lines

When creating the Python program, I take some information and put it in a list.

If you try to write this list to an Excel file, the data is all stored in the same block without new lines being created.

How do I get this data to create new lines using the comma as a separator.

Enter image description here

As you can see, no new lines are created. The data in my list is separated by commas, but Pandas does not create new rows.

Follow the code:

df = pd.DataFrame({'NAME':(Lawyer_Name),'OAB':(Lawyer_OAB)})

writer = pd.ExcelWriter('OABScrapperExcel.xlsx',engine = 'xlsxwriter')

df.to_excel(writer,sheet_name='LIST OF LAWYERS')

SQL Server – About 50% of tables in MS SQL have either 0, 1 or 2 lines – is it a good design?

First of all, I am neither a database programmer nor an administrator or someone responsible for this area. Therefore, I may be wrong in many of the following questions / assumptions.

I recently found a DB schema of about 250 tables. It is a database for an Eshop. I looked at many of these tables and was surprised how many of them were completely empty or had only 1 or 2 lines. So I checked all the tables with:

select count(*)
from sysobjects t, sysindexes i
where t.xtype = 'U' and = and i.indid in (0,1)
where i.rows in (0, 1, 2);


select count(*)
from sysobjects t, sysindexes i
where t.xtype = 'U' and = and i.indid in (0,1);

I found out that about 50% of all tables are tables with 0, 1 or 2 lines.

I understand that there are some rules for creating databases (regular forms), but this seems to me too much. For example, would not it be more efficient to save some of this data in a table than in two or more and then use joins? As I imagine, the database stores data in a table together (close to each other) on the hard drive so that they can be retrieved quickly. However, if I use two or more tables (therefore links must be used when retrieving the data), the data can be stored in different locations on the hard disk. Take more time to retrieve them.

I assume the database is not big. The largest tables have about 1 million lines. I think this could be considered small today. So it may not make much difference in this amount of data if I use joins extensively.

I know that my question is quite broad. Since I do not have any knowledge of database design, I can not be more specific, but I would appreciate some of your thoughts about it.


python – Is it ok to divide a single line of code with "" into several lines?

First, let's get rid of some things:

first_name = input("What's your first name? ")
last_name = input("What's your last name? ")

This is a single line of code:

print(f'Hello, { first_name.capitalize() } { last_name.capitalize() }')

What can also be written like this:

{ first_name.capitalize() } 
{ last_name.capitalize() }  

Both lines of code are exactly the same, but I think the second way looks better when debugging.

That may be a stupid question, but I'm curious if this is accepted in the program society.